Simplifi Platform API · for developers

Qualified e-signatures,
from your code.

Send documents for qualified (eIDAS) electronic signature and automate your document workflows with a clean REST API. Create your credentials in the app and make your first call in minutes.

View the API documentation Start Now

first-call.sh

# 1. Get an access token (OAuth2 client_credentials)
curl -X POST https://auth.simplifi.ro/realms/Simplifi/protocol/openid-connect/token \
  -d "grant_type=client_credentials" \
  -d "client_id=YOUR_CLIENT_ID" \
  -d "client_secret=YOUR_SECRET"

# 2. Create your first document
curl -X POST https://api.simplifi.ro/publicapi/v1/documents \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "name": "First contract",
        "signature_level": "QUALIFIED",
        "pdf_base64": "<base64 PDF>" }'

No API fee. No approval process.

The API is on for every Simplifi company account. There is no separate subscription, no waitlist and no sales call.

API fee

API access is included with your company account: no platform fee and no integration subscription.

Approvals needed

A company admin creates the API client in the app (API Settings) and gets the credentials on the spot.

Same cost as the app

API usage is part of your regular subscription, at the same prices as the web app. No API premium and no surprise invoice: if your balance runs out, you get a stable insufficient_*_balance error.

Two ways to integrate

One API, two principals. Pick the model that fits each call, or combine them in the same integration.

Send for signature(Sign with Simplifi)

You send the document. The recipient signs with their own account.

Your software uploads a PDF, adds the signers and sends. Each counterparty signs on the Simplifi platform with their own account and their own qualified certificate; you just collect the executed document. No enrollment and no certificate management on your side.

Create the document with an authenticated REST call (client_credentials token)
Add the signers and the signature placements
Redirect each signer to the returned signing_url
Signers sign on Simplifi with their qualified certificate
Download the signed PDF; track progress via webhooks or polling

Best for contracts, HR packs and anything countersigned.

User automation

Your software acts as one of your own users, with their consent.

A person at your company, with their own Simplifi account and qualified certificate, authorizes your application once via OAuth. Your software then drives their normal document workflows machine-to-machine, including signing with the user's own certificate by supplying their current TOTP code.

The user consents once (OAuth device grant or PKCE)
Store the offline token and exchange it for access tokens
Automate their workflows: documents, groups, retention
Sign with their certificate by supplying the current TOTP code

Best for bulk sending, archiving and in-house tooling.

Full details in the API documentation

Electronic signature integration, for any platform

The Simplifi eIDAS API covers the signing flows of applications that work with documents:

HR & recruiting

Employment contracts, addendums and personnel files signed at onboarding.

ERP & accounting

Supplier contracts and fiscal documents signed straight from the existing system.

Real estate

Pre-contracts, rental agreements and handover reports signed remotely.

Fintech & insurance

Client onboarding, policies and credit agreements with full legal value.

Healthcare

Patient consents and medical documents, signed at qualified level.

Marketplace & SaaS

Any platform that needs documents countersigned between its users.

Built for integration

eIDAS qualified, from a QTSP

Qualified signatures with the same legal value as handwritten ones across the EU, issued by a supervised Qualified Trust Service Provider.

OAuth2 + REST

Standard OAuth2 authentication, JSON in, JSON out, no mandatory proprietary SDKs.

Signed webhooks

document.signer.signed, document.completed, document.rejected, plus balance alerts. Every delivery is signed with HMAC-SHA256.

OpenAPI 3.1 spec

The complete API specification is public: generate clients and tests straight from it.

Postman collection

A personalized Postman environment and code samples in the in-app developer portal.

Test environment

Test your integration end-to-end in the development environment (app.dev.simplifi.ro) before going to production.

Download the OpenAPI 3.1 spec Open the Postman collection Code samples on GitHub

Embedded Signing: partner program

For a deeper, white-label integration: identity verification, qualified certificate issuance and signing run entirely inside your product, and your signers never need a Simplifi account. It is a separate partner program, by application, individually reviewed and subscription-based.

Talk to us

API frequently asked questions

Can I integrate qualified signing directly into my platform?

Yes, that is the User automation model. A user with a qualified certificate consents once via OAuth, then your software drives their document workflows machine-to-machine and signs with their certificate by supplying their current TOTP code, without the user ever leaving your platform. For documents signed by third parties you use Send for signature: the counterparty signs on Simplifi with their own account and certificate.

How much does using the API cost?

API usage is part of your regular subscription: the same credits and the same prices as the web app, whether you send documents for signature or automate a user's account. There is no API fee, no separate subscription and no API premium. If your balance runs out, the API returns a stable insufficient_*_balance error you can handle in your application.

Do I need approval to start?

No. A company admin creates the API client in the app, under API Settings, and gets the credentials on the spot. There is nothing to apply for and nobody to wait on.

Do my recipients need a Simplifi account?

In the Send for signature model, yes: each signer signs on the Simplifi platform with their own account (full, guest or sponsored) and their own qualified certificate. Your application redirects the signer to the signing URL returned by the API, tracks progress via webhooks and downloads the executed document.

Is there a test environment?

Yes. You can test your integration against the development environment: the app runs at app.dev.simplifi.ro, the API and its docs at api.dev.simplifi.ro. Production uses api.simplifi.ro, with the same APIs.

Are there rate limits?

Yes, and they are published in the API documentation: 1800 requests per minute for integration tokens and 600 requests per minute for user tokens. Generous limits for typical document workflows.

Make your first call today

The documentation is public, the credentials are self-service, and the costs are per use. From zero to an authenticated call in three steps.