V1
Sign Configuration
Sign Configuration
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| org_id | path | string | true | Organization name |
Request example
|
|
Responses
| Code | Meaning | Description | Schema |
|---|---|---|---|
| 200 | OK | Sign configuration of given tenant. | SignConfiguration |
| 400 | Bad Request | Request input is not valid | None |
| 401 | Unauthorized | Unauthorized. AuthN and AuthZ validations have fail or certificate password is not correct | None |
| 500 | Internal Server Error | Not expected error | None |
| default | Default | Error response | ErrorsResponse |
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| org_id | path | string | true | Organization name |
| body | body | object | true | Data about sign configuration |
Request body - Content-Type: multipart/form-data
Custom schema example
|
|
| Name | Type | Required | Description |
|---|---|---|---|
| landing_url | string | true | Sign process URL |
| expiration_duration | string | true | Validity duration time (ISO-8601 format) of any sign process for the tenant. |
| channels | array | true | Channels to send notifications. Possible values: SMS, EMAIL, or WHATSAPP. |
| content | string | true | The PKCS#12 (.p12) certificate file |
| sign_certificate_password | string | true | Password for the PKCS#12 certificate |
| notification_email | string | true | Email where the notifications about certificate expiration will be sent |
Request example
|
|
Responses
| Code | Meaning | Description | Schema |
|---|---|---|---|
| 204 | No Content | New sign configuration is created. | None |
| 400 | Bad Request | Request input is not valid | None |
| 401 | Unauthorized | Unauthorized. AuthN and AuthZ validations have fail or certificate password is not correct | None |
| 500 | Internal Server Error | Not expected error | None |
| default | Default | Error response | ErrorsResponse |
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| org_id | path | string | true | Organization name |
| body | body | ConfigurationPatchRequest | true | Data about sign configuration |
|
|
| Name | Type | Required | Description |
|---|---|---|---|
| landing_url | LandingUrl | false | Sign process URL |
| expiration_duration | ExpirationDuration | false | Validity duration time (ISO-8601 format) of any sign process for the tenant. |
| channels | NotificationChannels | false | Channels to send notifications. Possible values: SMS, EMAIL, or WHATSAPP. |
| content | SignCertificateContent | false | The PKCS#12 (.p12) certificate file |
| sign_certificate_password | SignCertificatePassword | false | Password for the PKCS#12 certificate |
| notification_email | NotificationEmail | false | Email where the notifications about certificate expiration will be sent |
Request example
|
|
Responses
| Code | Meaning | Description | Schema |
|---|---|---|---|
| 204 | No Content | Sign configuration is created. | None |
| 400 | Bad Request | Request input is not valid | None |
| 401 | Unauthorized | Unauthorized. AuthN and AuthZ validations have fail or certificate password is not correct | None |
| 500 | Internal Server Error | Not expected error | None |
| default | Default | Error response | ErrorsResponse |
Endpoints
Documents
Forms
Sections
Templates
Templates Configuration
DynamicTemplates
Digital Sign Process
Biometric Signature
Simple Signature
Identification Agent
Sign Configuration
Identification OTP
Identification with identity document
Identification Agent Admin
Identification OTP Admin
Identification with identity document Admin
Contracts
Scoring
Securize
Identification Chain
Identification Chain Admin