Skip to main content

Everything the interface does, the API does

Send envelopes, require checks and pull back sealed files from your own systems. Embed the signing view in your product, or run the whole platform on your infrastructure under your own certificate authority.

Get startedSee the signing flow

How Platform works

  • Drive it from your own systems

    Create an envelope, attach recipients, require a check, and collect the sealed PDF when it comes back. The API is the same one the interface calls, so nothing you can do on screen is missing from it.

    • A published OpenAPI specification, with reference documentation generated from it
    • Signed webhooks for every state an envelope passes through
    • Per-team tokens, so a revoked integration takes nothing else with it
    curl https://api-staging.sedeya.com/v1/envelopes \
  -H "Authorization: Bearer $SEDEYA_TOKEN" \
  -F "document=@contrat-pret.pdf" \
  -F "recipients[0][email]=a.diallo@example.gn" \
  -F "recipients[0][verify]=identity"

    Read the API reference

  • Keep the signer inside your product

    Open the signing view in your own application rather than sending the signer somewhere else. Your interface, your domain, the same sealed output and the same audit trail underneath.

    • The signing view opens in your page, not on a redirect
    • Your branding on the document the signer sees
    • Events reach your application as they happen, not by polling

  • Run it on your own infrastructure

    The whole platform, deployed inside your network, sealing documents under a certificate authority you control. Nothing leaves your infrastructure, and the trust chain in the finished PDF is yours rather than ours.

    • Deployed on infrastructure you operate, in a network you control
    • Documents sealed under your own certificate authority
    • The same API and the same sealed output as the hosted platform

What's included in Platform

The specification is published rather than described. Generate a client in your language from it. Reference documentation is generated from the same file.

Every envelope event carries a signature you verify against a secret only your team holds, so your endpoint can tell our call from anyone else's.

Tokens are issued per team rather than per account. Revoking one integration stops that integration and nothing else.

An envelope created by the API produces the same certificate page and the same audit log as one created on screen. There is no second, lesser record for programmatic work.

Run it yourself, seal it yourself

Hosted, the trust chain in a finished document is ours. Self-hosted, it is yours — and that is the difference no hosted-only platform can offer you.

  • Your infrastructure, your network

    The platform runs where you put it. Documents, checks and audit records stay inside the network you operate, and no part of the flow leaves it.

  • Your certificate authority

    Documents are sealed under a certificate authority you control rather than one we control. The seal in the finished PDF chains back to your organisation.

  • The same output either way

    A self-hosted deployment produces the same sealed PDF, the same certificate page and the same audit log as the hosted platform. The difference is who holds the key, not what comes out.

  • The same API either way

    Code written against the hosted API runs against a self-hosted deployment unchanged. Moving from one to the other is a change of address, not a rewrite.

An API that can do less than the interface it sits under is a support burden pretending to be a product. Ours is the same one the screens call, which is not generosity — it is the only arrangement where the two cannot drift apart.

Self-hosting is here for the same reason the rest of the platform is. A bank or a ministry that cannot let documents leave its network is not asking for a feature; it is describing the only terms on which it can work at all. Running under your own certificate authority means the trust in a finished document traces back to your organisation rather than to ours, and that is not something a hosted-only platform can hand you later.

The rest of the product set

The other pieces of the platform, and what each one does.

E-signatureSend a contract, get it back signed the same day — sealed, with its certificate and audit trail inside the PDF itself.E-verification
Early access
Check a person, a company or a bank account online, and get back a result you can keep. Minutes, not a week of emails and scanned documents.

Frequently asked questions

A bearer token, issued per team, sent in the Authorization header. Tokens are created and revoked from your team settings, and revoking one affects only the integration that used it. Nothing else in your account changes.

Every webhook carries a signature computed over the request body with a secret only your team holds. Recompute it on your side and compare — if it does not match, the call is not ours. The secret is visible once when the endpoint is created and can be rotated at any time.

Somewhere to run the platform inside your network, a database, and a certificate authority you control for sealing. We walk your team through the deployment and the certificate setup, and the result speaks the same API as the hosted platform.

Bring Platform to your team

Talk to us about rolling it out, or start today if it is already live.

Get started