| CreateTransactionRequest | Transaction creation data including signers, receivers, files, and configuration. This is the request body for creating a new transaction. |
| Transaction | Complete transaction data returned when retrieving or creating a transaction. Includes all configuration, current status, and file information. |
| CreateSignerRequest | Request object for creating a new signer in a transaction. Defines the signer's identity, authentication/verification requirements, notification preferences, and signing behavior. Key Requirements: - Email address is mandatory - Either Authentications or Verifications must be provided (or both) - Signers with AllowDelegation enabled cannot have Authentications - SendSignRequest determines if sign request emails are sent automatically |
| Signer | Signer information with current status (based on SignerGetDto which extends SignerBaseDto) |
| CreateReceiverRequest | Receiver configuration for getting copies of signed documents |
| Receiver | Receiver information (based on ReceiverGetDto which extends ReceiverBaseDto) |
| SignerAuthentication | Authentication methods used to verify signer identity before document access. These methods must be completed before the signer can view documents. Important: The "Type" property is case-sensitive and must be capitalized. |
| SignerVerification | Verification methods used to confirm signer identity before document signing. These methods must be completed before the signer can sign documents. Important: The "Type" property is case-sensitive and must be capitalized. Critical Requirement: You must use one of the following verification methods as the last verification in your verifications list: - Consent - PhoneNumber - Scribble - CSC Qualified* Rules for CSC Qualified: - This method must always be the absolute final verification - nothing can come after it Rules for Consent, PhoneNumber, and Scribble: - These three can be used as the final verification method - They are commonly used when you want additional verification steps before the final consent/signature Common Mistakes: - Using only authentication methods (e.g., iDIN) without a final verification method - Placing verifications after CSC Qualified Valid Examples: - [Consent] ✓ - [iDIN, Consent] ✓ - [iDIN, PhoneNumber] ✓ - [iDIN, CSC Qualified] ✓ - [CSC Qualified, Consent] ✗ (Nothing can come after CSC Qualified) - [iDIN] ✗ (Missing required final verification) |
| SignerScribbleVerification | Handwritten signature verification |
| SignerEmailVerification | Email address verification |
| SignerPhoneNumberIdentification | SMS phone number verification |
| SignerDigidIdentification | Dutch DigiD verification |
| SignerIDealVerification | iDEAL bank verification |
| SignerSurfnetVerification | SURFnet academic verification |
| SignerIDINVerification | iDIN bank identification verification |
| SignerIPAddressVerification | IP address verification |
| SignerEHerkenningVerification | eHerkenning business identity verification |
| SignerEidasLoginVerification | eIDAS electronic identification verification |
| SignerItsmeIdentificationVerification | itsme identification verification |
| SignerConsentVerification | Consent-based verification |
| SignerCscVerification | Cloud Signature Consortium (CSC) verification |
| SignerOidcIdentification | OpenID Connect identification |
| SignerOnfidoIdentification | Onfido identity verification |
| FileEntry | File information and metadata associated with a transaction. Contains details about uploaded documents including display properties, download links, and current processing status. Files are referenced by their unique identifier within the transaction and can include PDFs, receipts, and other document types. |
| Link | URI link with relationship and type information |
| Activity | Activity/event information for a signer (based on ActivityGetDto) |
| FileMetadata | Comprehensive metadata information for a file in a transaction. This metadata defines how the file should be displayed, processed, and what form fields and signing areas it contains. The metadata can be uploaded before or after the actual PDF file. |
| FileSignerData | Configuration data specific to a signer for a particular file. This determines which form sets the signer needs to complete when signing the document. |
| FileField | Represents an individual form field or signing area within a document. Fields define where and how users interact with the document during the signing process. |
| FileFieldType | Specifies the type of interaction or data entry required for this field. Different types have different behaviors and validation rules in the signing interface. |
| FileFieldLocation | Defines the precise positioning and sizing of a field within the PDF document. Fields can be positioned using absolute coordinates or by searching for specific text anchors within the document. |
| TransactionDeleteOptions | Options for cancelling a transaction |
| ErrorResponse | Error response object based on RFC 7807 Problem Details for HTTP APIs. See https://datatracker.ietf.org/doc/html/rfc7807 for details. Response Format: A response is either in the new RFC 7807 Problem Details format OR the legacy Message format, but never both. - New Format (RFC 7807): Contains the type property and standard problem detail properties (title, detail, status). May also include additional extension members. - Legacy Format: Contains only the Message property. This format is used for some existing error responses during our transition to full RFC 7807 compliance. Usage: Check if the type property is present. If it exists, the response is in RFC 7807 format. If type is absent, fall back to reading the Message property. |
