Developer Portal

Techsign DOC

Add secure, legally valid biometric signatures to your own software and run contract workflows end to end without paper.

Every service in one place

Document, template, signature, signing, user, organisation and audit services, with their request and response models.

Try it in your browser

Get an access token with your client credentials and call the endpoints straight from the API Reference.

Always current

The reference comes from Techsign DOC's live API definition, so new services show up as they are added.

About Techsign DOC#

Techsign DOC brings creating, signing, tracking and storing your contracts into one platform. With the API you embed the same process in your own software: prepare the document from your data, send it for signature, follow its status and get the signed document back.

A typical integration#

  1. Create the document. Upload a PDF or generate a document from a saved template, and prefill its signature and content fields with data from your system.
  2. Send it for signature. Set the recipients and the signing order; the document is signed remotely through an e-mail, SMS or WhatsApp link, or in person on a tablet.
  3. Track it. Query the signing status and send reminders to recipients who haven't signed yet.
  4. Get the document and the evidence. Download the signed PDF and its audit trail, with the timestamp, date, location and IP details.

What you can customise#

  • Content objects: Shape the document to your flow with fields and objects.
  • Prefilled fields: Write customer, contract and product data into the fields automatically.
  • Signing order: Decide who receives the document and in which order, sequentially or in parallel.
  • Sending on behalf of the organisation: Send documents on behalf of users in your organisation.
  • Signature type: Biometric, draw-to-sign or click-to-sign, whichever fits the scenario.

Authentication#

The API uses the OAuth 2.0 client credentials flow. Request an access token from https://api.techsigndoc.com/oauth/access_token with your organisation's client_id and client_secret, then send it as an Authorization: Bearer <token> header on every call.

Note

Keep the client credentials on your server. Never ship the client_secret in a browser or mobile app.

Security#

  • The APIs are served over HTTPS only, with an SSL certificate.
  • Requests are rate-limited per IP: above a set number in a given window, requests are rejected.
  • Requests whose payload looks like an attack are blocked.
  • Independent specialist firms test the server code for security and run code analysis on it.

Getting live#

Without development work you can go live within 24 hours; integrations that need development usually finish within a week. Throughout, we answer your questions by e-mail, meet online when needed and share a Postman collection tailored to your flow.

Need access credentials?

To call the API you need your organisation's credentials. Your Techsign representative can set them up for you.

Contact us