Integrations & API — found from sitemap — Signicat Sign

Cited by

Facts read from this source

• API base URL Report an error

  “url = 'https://api.signicat.com/sign/documents'”

• Upload document formats Report an error

  “We support both PDFs and plain text documents, and the operation is as simple as making an HTTP POST request with the document's binary data to the Documents endpoint of the API.”

• Pades packaging Report an error

  “Here, we want the signed document to be a PAdES (PDF Advanced Electronic Signatures), so we set it to PADES_CONTAINER.”

• Packaging async webhook Report an error

  “However, packaging is an asynchronous process. This means that when the end-user returns to your application after signing, the PAdES is most likely not produced yet.”

• Webhook events Report an error

  “we have set up a webhook subscription for the events 'Packaging completed' and 'Packaging failed', under the 'Signature' label in the Dashboard.”

• Signing session deadline Report an error

  “dueDate (optional): If you omit this field, the signing deadline defaults to 30 days after session creation. You can explicitly set a deadline up to 45 days into the future.”

• Multi signer parallel authentication Report an error

  “For authentication-based signing (for example, Freja, MitID, FTN, iDIN, SMS OTP, Email OTP), the process allows multiple signers to sign a document in parallel.”

• Norwegian bankid pki locking Report an error

  “When using Norwegian BankID PKI, multiple signers can sign the document in any order (unordered signing). Because PKI signing requires modifying the document sequentially, Sign API v2 handles this using an automatic locking mechanism for Norwegian BankID PKI signing.”

• Signature forwarding Report an error

  “Signature forwarding allows end-users to send a signing session to another person and nominate that person as a signer.”

• Mandatory view only documents Report an error

  “It is possible to add mandatory view-only documents (such as terms and conditions documents or privacy policies) to a signing session.”

• View only excluded from archive Report an error

  “They are not digitally signed, they are not included in the final packaged PAdES container (the signed PDF result) and they are not sent to the long-term document archive.”

• Text signing Report an error

  “Simple text signing allows you to present a plain text string for the user to sign instead of a PDF document.”

• Merchant signing Report an error

  “Merchant signing (also known as sealing) allows your organisation to sign or seal documents automatically without any end-user interaction.”

• Rejection with reason Report an error

  “End-users have the option to reject a signing session instead of completing or cancelling it. When rejecting, the user can provide a specific reason for the rejection”

• Pre authentication Report an error

  “The preAuthentication.identityProviders property controls which identity providers the signer can use to pre-authenticate before viewing the document(s)”

• Requested attributes Report an error

  “You can request identity provider-specific extra attributes by including a requestedAttributes array inside the signingSetup object.”

• Signing flows Report an error

  “In our simple scenario, we set signingFlow to AUTHENTICATION_BASED. Other options are available but omitted here for brevity.”

• Permission required Report an error

  “Ensure that you set permission Signature API for your API client.”

• API reference Report an error

  “Explore our Sign API v2 reference documentation to look up all API endpoints and properties as well as view sample requests and responses.”

• Claim Report an error

  “Regulatory compliant electronic signatures”

• Signature type in output Report an error

  “"signatureType": "XADES"”

• Lifecycle docs Report an error

  “For details on how long documents are stored and what happens when sessions expire or documents are deleted, see our Document retention and deletion lifecycle guide.”

• Notifications email sms Report an error

  “notifications can be included with outgoing communication messages (email, SMS) so that messages can be correlated or filtered by tag.”

3 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The Data Protection Officer eIDAS levels & trust services
• The Data Protection Officer Signer identification
• The Data Protection Officer Signing workflow & signer experience
• The Data Protection Officer Evidence, validation & retention
• The Data Protection Officer Integrations & API
• The HR Operations Lead eIDAS levels & trust services
• The HR Operations Lead Signer identification
• The HR Operations Lead Signing workflow & signer experience
• The HR Operations Lead Evidence, validation & retention
• The HR Operations Lead Integrations & API
• The Integration Engineer eIDAS levels & trust services
• The Integration Engineer Signer identification
• The Integration Engineer Signing workflow & signer experience
• The Integration Engineer Evidence, validation & retention
• The Integration Engineer Integrations & API
• The Legal Counsel eIDAS levels & trust services
• The Legal Counsel Signer identification
• The Legal Counsel Signing workflow & signer experience
• The Legal Counsel Evidence, validation & retention
• The Legal Counsel Integrations & API
• The Revenue Operations Lead eIDAS levels & trust services
• The Revenue Operations Lead Signer identification
• The Revenue Operations Lead Signing workflow & signer experience
• The Revenue Operations Lead Evidence, validation & retention
• The Revenue Operations Lead Integrations & API
• The Skeptic eIDAS levels & trust services
• The Skeptic Signer identification
• The Skeptic Signing workflow & signer experience
• The Skeptic Evidence, validation & retention
• The Skeptic Integrations & API