|
PowerForm | CreatePowerForm (string accountId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
ApiResponse< PowerForm > | CreatePowerFormWithHttpInfo (string accountId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
void | DeletePowerForm (string accountId, string powerFormId) |
| Delete a PowerForm. More...
|
|
ApiResponse< Object > | DeletePowerFormWithHttpInfo (string accountId, string powerFormId) |
| Delete a PowerForm. More...
|
|
PowerFormsResponse | DeletePowerForms (string accountId, PowerFormsRequest powerFormsRequest=null) |
| Deletes one or more PowerForms More...
|
|
ApiResponse< PowerFormsResponse > | DeletePowerFormsWithHttpInfo (string accountId, PowerFormsRequest powerFormsRequest=null) |
| Deletes one or more PowerForms More...
|
|
PowerForm | GetPowerForm (string accountId, string powerFormId) |
| Returns a single PowerForm. More...
|
|
ApiResponse< PowerForm > | GetPowerFormWithHttpInfo (string accountId, string powerFormId) |
| Returns a single PowerForm. More...
|
|
PowerFormsFormDataResponse | GetPowerFormData (string accountId, string powerFormId, PowerFormsApi.GetPowerFormDataOptions options=null) |
| Returns the form data associated with the usage of a PowerForm. More...
|
|
ApiResponse< PowerFormsFormDataResponse > | GetPowerFormDataWithHttpInfo (string accountId, string powerFormId, PowerFormsApi.GetPowerFormDataOptions options=null) |
| Returns the form data associated with the usage of a PowerForm. More...
|
|
PowerFormSendersResponse | ListPowerFormSenders (string accountId, PowerFormsApi.ListPowerFormSendersOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
ApiResponse< PowerFormSendersResponse > | ListPowerFormSendersWithHttpInfo (string accountId, PowerFormsApi.ListPowerFormSendersOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
PowerFormsResponse | ListPowerForms (string accountId, PowerFormsApi.ListPowerFormsOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
ApiResponse< PowerFormsResponse > | ListPowerFormsWithHttpInfo (string accountId, PowerFormsApi.ListPowerFormsOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
PowerForm | UpdatePowerForm (string accountId, string powerFormId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
ApiResponse< PowerForm > | UpdatePowerFormWithHttpInfo (string accountId, string powerFormId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
System.Threading.Tasks.Task< PowerForm > | CreatePowerFormAsync (string accountId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerForm > > | CreatePowerFormAsyncWithHttpInfo (string accountId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
System.Threading.Tasks.Task | DeletePowerFormAsync (string accountId, string powerFormId) |
| Delete a PowerForm. More...
|
|
System.Threading.Tasks.Task< ApiResponse< Object > > | DeletePowerFormAsyncWithHttpInfo (string accountId, string powerFormId) |
| Delete a PowerForm. More...
|
|
System.Threading.Tasks.Task< PowerFormsResponse > | DeletePowerFormsAsync (string accountId, PowerFormsRequest powerFormsRequest=null) |
| Deletes one or more PowerForms More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerFormsResponse > > | DeletePowerFormsAsyncWithHttpInfo (string accountId, PowerFormsRequest powerFormsRequest=null) |
| Deletes one or more PowerForms More...
|
|
System.Threading.Tasks.Task< PowerForm > | GetPowerFormAsync (string accountId, string powerFormId) |
| Returns a single PowerForm. More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerForm > > | GetPowerFormAsyncWithHttpInfo (string accountId, string powerFormId) |
| Returns a single PowerForm. More...
|
|
System.Threading.Tasks.Task< PowerFormsFormDataResponse > | GetPowerFormDataAsync (string accountId, string powerFormId, PowerFormsApi.GetPowerFormDataOptions options=null) |
| Returns the form data associated with the usage of a PowerForm. More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerFormsFormDataResponse > > | GetPowerFormDataAsyncWithHttpInfo (string accountId, string powerFormId, PowerFormsApi.GetPowerFormDataOptions options=null) |
| Returns the form data associated with the usage of a PowerForm. More...
|
|
System.Threading.Tasks.Task< PowerFormSendersResponse > | ListPowerFormSendersAsync (string accountId, PowerFormsApi.ListPowerFormSendersOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerFormSendersResponse > > | ListPowerFormSendersAsyncWithHttpInfo (string accountId, PowerFormsApi.ListPowerFormSendersOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
System.Threading.Tasks.Task< PowerFormsResponse > | ListPowerFormsAsync (string accountId, PowerFormsApi.ListPowerFormsOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerFormsResponse > > | ListPowerFormsAsyncWithHttpInfo (string accountId, PowerFormsApi.ListPowerFormsOptions options=null) |
| Returns the list of PowerForms available to the user. More...
|
|
System.Threading.Tasks.Task< PowerForm > | UpdatePowerFormAsync (string accountId, string powerFormId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
System.Threading.Tasks.Task< ApiResponse< PowerForm > > | UpdatePowerFormAsyncWithHttpInfo (string accountId, string powerFormId, PowerForm powerForm=null) |
| Creates a new PowerForm. More...
|
|
String | GetBasePath () |
| Gets the base path of the API client. More...
|
|
Represents a collection of functions to interact with the API endpoints
PowerForm DocuSign.eSign.Api.IPowerFormsApi.CreatePowerForm |
( |
string |
accountId, |
|
|
PowerForm |
powerForm = null |
|
) |
| |
Creates a new PowerForm.
This method creates a new PowerForm. You create a PowerForm from an existing DocuSign template, based on the `templateId` in the request body. PowerForms that you create from a template are referred to as web PowerForms. Note: The DocuSign Admin console also supports creating a PowerForm by uploading a PDF file that has active form fields (referred to as a PDF PowerForm). However, PDF PowerForms are deprecated and are not supported in the API. Note: A PowerForm can have only one sender. (Because PowerForms are not necessarily sent by email, this user is also referred to as the PowerForm initiator.) If you need to associate multiple senders with a PowerForm, create multiple copies of the PowerForm by using the same template (one copy for each sender). By default, the sender is the PowerForm Administrator who creates the PowerForm. ### Signing modes You can use one of the following signing modes for a PowerForm: `email` This mode verifies the recipient's identity by using email authentication before the recipient can sign a document. The recipient enters their email address on the landing page and then clicks Begin Signing to begin the signing process. The system then sends an email message with a validation code to the recipient. If the recipient does not provide a valid email address, they do not receive the email message containing the access code and are not able to open and sign the document. Alternatively, you can make the process easier for signers by using email authentication only and omitting the access code. To do this, you append the `activateonly` flag to the PowerForm URL and set it to true by passing in the value `1`. When the flag is active, the first recipient receives an email with a link that initiates the signing session without having to enter access code. Example: `activateonly=1` `direct` This mode does not require any verification. After a recipient enters their email address on the landing page and clicks Begin Signing, a new browser tab opens and the recipient can immediately begin the signing process. Because the `direct` signing mode does not verify the recipient's identity by using email authentication, we strongly recommend that you use this mode only when the PowerForm is accessible behind a secure portal where the recipient's identity is already authenticated, or where another form of authentication is specified for the recipient in the DocuSign template (for example, an access code, phone authentication, or ID check). Note: In the account settings, `enablePowerFormDirect` must be true to use `direct` as the `signingMode`. ### Redirect URLs You can control the URL to which signers are redirected after signing your PowerForm. However, the URL is specified elsewhere, outside of the PowerForm creation process. For details, see How do I specify a URL to redirect to when a PowerForm is completed?. ### More information For more information about creating PowerForms, see Create a PowerForm.
- Exceptions
-
- Parameters
-
accountId | The external account number (int) or account ID Guid. |
powerForm | (optional) |
- Returns
Implemented in DocuSign.eSign.Api.PowerFormsApi.
System.Threading.Tasks.Task<PowerForm> DocuSign.eSign.Api.IPowerFormsApi.CreatePowerFormAsync |
( |
string |
accountId, |
|
|
PowerForm |
powerForm = null |
|
) |
| |
Creates a new PowerForm.
This method creates a new PowerForm. You create a PowerForm from an existing DocuSign template, based on the `templateId` in the request body. PowerForms that you create from a template are referred to as web PowerForms. Note: The DocuSign Admin console also supports creating a PowerForm by uploading a PDF file that has active form fields (referred to as a PDF PowerForm). However, PDF PowerForms are deprecated and are not supported in the API. Note: A PowerForm can have only one sender. (Because PowerForms are not necessarily sent by email, this user is also referred to as the PowerForm initiator.) If you need to associate multiple senders with a PowerForm, create multiple copies of the PowerForm by using the same template (one copy for each sender). By default, the sender is the PowerForm Administrator who creates the PowerForm. ### Signing modes You can use one of the following signing modes for a PowerForm: `email` This mode verifies the recipient's identity by using email authentication before the recipient can sign a document. The recipient enters their email address on the landing page and then clicks Begin Signing to begin the signing process. The system then sends an email message with a validation code to the recipient. If the recipient does not provide a valid email address, they do not receive the email message containing the access code and are not able to open and sign the document. Alternatively, you can make the process easier for signers by using email authentication only and omitting the access code. To do this, you append the `activateonly` flag to the PowerForm URL and set it to true by passing in the value `1`. When the flag is active, the first recipient receives an email with a link that initiates the signing session without having to enter access code. Example: `activateonly=1` `direct` This mode does not require any verification. After a recipient enters their email address on the landing page and clicks Begin Signing, a new browser tab opens and the recipient can immediately begin the signing process. Because the `direct` signing mode does not verify the recipient's identity by using email authentication, we strongly recommend that you use this mode only when the PowerForm is accessible behind a secure portal where the recipient's identity is already authenticated, or where another form of authentication is specified for the recipient in the DocuSign template (for example, an access code, phone authentication, or ID check). Note: In the account settings, `enablePowerFormDirect` must be true to use `direct` as the `signingMode`. ### Redirect URLs You can control the URL to which signers are redirected after signing your PowerForm. However, the URL is specified elsewhere, outside of the PowerForm creation process. For details, see How do I specify a URL to redirect to when a PowerForm is completed?. ### More information For more information about creating PowerForms, see Create a PowerForm.
- Exceptions
-
- Parameters
-
accountId | The external account number (int) or account ID Guid. |
powerForm | (optional) |
- Returns
- Task of PowerForm
Implemented in DocuSign.eSign.Api.PowerFormsApi.
System.Threading.Tasks.Task<ApiResponse<PowerForm> > DocuSign.eSign.Api.IPowerFormsApi.CreatePowerFormAsyncWithHttpInfo |
( |
string |
accountId, |
|
|
PowerForm |
powerForm = null |
|
) |
| |
Creates a new PowerForm.
This method creates a new PowerForm. You create a PowerForm from an existing DocuSign template, based on the `templateId` in the request body. PowerForms that you create from a template are referred to as web PowerForms. Note: The DocuSign Admin console also supports creating a PowerForm by uploading a PDF file that has active form fields (referred to as a PDF PowerForm). However, PDF PowerForms are deprecated and are not supported in the API. Note: A PowerForm can have only one sender. (Because PowerForms are not necessarily sent by email, this user is also referred to as the PowerForm initiator.) If you need to associate multiple senders with a PowerForm, create multiple copies of the PowerForm by using the same template (one copy for each sender). By default, the sender is the PowerForm Administrator who creates the PowerForm. ### Signing modes You can use one of the following signing modes for a PowerForm: `email` This mode verifies the recipient's identity by using email authentication before the recipient can sign a document. The recipient enters their email address on the landing page and then clicks Begin Signing to begin the signing process. The system then sends an email message with a validation code to the recipient. If the recipient does not provide a valid email address, they do not receive the email message containing the access code and are not able to open and sign the document. Alternatively, you can make the process easier for signers by using email authentication only and omitting the access code. To do this, you append the `activateonly` flag to the PowerForm URL and set it to true by passing in the value `1`. When the flag is active, the first recipient receives an email with a link that initiates the signing session without having to enter access code. Example: `activateonly=1` `direct` This mode does not require any verification. After a recipient enters their email address on the landing page and clicks Begin Signing, a new browser tab opens and the recipient can immediately begin the signing process. Because the `direct` signing mode does not verify the recipient's identity by using email authentication, we strongly recommend that you use this mode only when the PowerForm is accessible behind a secure portal where the recipient's identity is already authenticated, or where another form of authentication is specified for the recipient in the DocuSign template (for example, an access code, phone authentication, or ID check). Note: In the account settings, `enablePowerFormDirect` must be true to use `direct` as the `signingMode`. ### Redirect URLs You can control the URL to which signers are redirected after signing your PowerForm. However, the URL is specified elsewhere, outside of the PowerForm creation process. For details, see How do I specify a URL to redirect to when a PowerForm is completed?. ### More information For more information about creating PowerForms, see Create a PowerForm.
- Exceptions
-
- Parameters
-
accountId | The external account number (int) or account ID Guid. |
powerForm | (optional) |
- Returns
- Task of ApiResponse (PowerForm)
Implemented in DocuSign.eSign.Api.PowerFormsApi.
Creates a new PowerForm.
This method creates a new PowerForm. You create a PowerForm from an existing DocuSign template, based on the `templateId` in the request body. PowerForms that you create from a template are referred to as web PowerForms. Note: The DocuSign Admin console also supports creating a PowerForm by uploading a PDF file that has active form fields (referred to as a PDF PowerForm). However, PDF PowerForms are deprecated and are not supported in the API. Note: A PowerForm can have only one sender. (Because PowerForms are not necessarily sent by email, this user is also referred to as the PowerForm initiator.) If you need to associate multiple senders with a PowerForm, create multiple copies of the PowerForm by using the same template (one copy for each sender). By default, the sender is the PowerForm Administrator who creates the PowerForm. ### Signing modes You can use one of the following signing modes for a PowerForm: `email` This mode verifies the recipient's identity by using email authentication before the recipient can sign a document. The recipient enters their email address on the landing page and then clicks Begin Signing to begin the signing process. The system then sends an email message with a validation code to the recipient. If the recipient does not provide a valid email address, they do not receive the email message containing the access code and are not able to open and sign the document. Alternatively, you can make the process easier for signers by using email authentication only and omitting the access code. To do this, you append the `activateonly` flag to the PowerForm URL and set it to true by passing in the value `1`. When the flag is active, the first recipient receives an email with a link that initiates the signing session without having to enter access code. Example: `activateonly=1` `direct` This mode does not require any verification. After a recipient enters their email address on the landing page and clicks Begin Signing, a new browser tab opens and the recipient can immediately begin the signing process. Because the `direct` signing mode does not verify the recipient's identity by using email authentication, we strongly recommend that you use this mode only when the PowerForm is accessible behind a secure portal where the recipient's identity is already authenticated, or where another form of authentication is specified for the recipient in the DocuSign template (for example, an access code, phone authentication, or ID check). Note: In the account settings, `enablePowerFormDirect` must be true to use `direct` as the `signingMode`. ### Redirect URLs You can control the URL to which signers are redirected after signing your PowerForm. However, the URL is specified elsewhere, outside of the PowerForm creation process. For details, see How do I specify a URL to redirect to when a PowerForm is completed?. ### More information For more information about creating PowerForms, see Create a PowerForm.
- Exceptions
-
- Parameters
-
accountId | The external account number (int) or account ID Guid. |
powerForm | (optional) |
- Returns
- ApiResponse of
Implemented in DocuSign.eSign.Api.PowerFormsApi.