Skip to content
For developers

The photo proof API.

Open a capture page in your brand from your app, and get back a sealed proof: a qualified eIDAS timestamp, a C2PA signature and a public verification link. Plain JSON over HTTPS.

  • Qualified eIDAS timestamp
  • C2PA conformant (photos)
  • Open-source verifier
  • Free test mode, no card
Your logo, your color and your texts, in your users' language. The capture page is a web page your app opens.
The problem

The timestamp is the easy part. Everything around it isn't.

Building photo proof yourself means running a whole chain before the first photo holds up.

  • Qualified timestamps and signaturesA contract with a qualified trust service, signing keys, certificate chains and C2PA manifests: to buy, run and renew.
  • A capture you can trustA camera flow that refuses gallery imports, sends files straight to storage and speaks your users' language.
  • Proof a third party can checkOriginals stored unchanged, a public verification page, and a way to check a proof without trusting your servers.
The API

One API, service by service.

Each card leads to its page in the documentation.

  • Capture sessions

    Create a one-time capture link for a transaction and open it from your app: a white-labeled page for live photos.

    • POST /v1/capture-sessions
  • Proofs

    Follow each proof from capture to seal, read its status and its files, and find it by your own reference.

    • GET /v1/proofs
    • GET /v1/proofs/{id}
  • Verify

    A public verification page anyone can open, without an account, and an open-source verifier (MIT) to check a proof without us.

    • GET /v1/public/proofs/{id}
  • Signed webhooks

    Be told on your server the moment a proof is sealed. Every delivery is signed and logged, and you can send a test event.

    • POST /v1/webhook-endpoints
  • Templates and appearance

    Choose the shots and the texts in every language, and the look of the capture page: your logo and your color.

    • POST /v1/capture-templates
    • POST /v1/capture-themes
  • Return to your app

    Bring the person back to your app after the last photo, to an address you declared beforehand.

    • return_url
Toolbox

Use it from the tools you already have.

The packages are published on npm under the MIT licence.

Get started

From account to production in four steps.

  1. 01

    Create an account

    Free, no card. €5 offered, usable in production.

  2. 02

    Create a test key

    In your dashboard, under API keys. It starts with sk_test_: keep it in an environment variable, never in code.

  3. 03

    Seal a first test proof

    Create a capture session, open the link on a phone, take the photos and receive the proof.sealed webhook. Simulated timestamps, nothing billed.

  4. 04

    Go live

    Switch to a live key: each sealed proof gets a qualified eIDAS timestamp and is debited from your balance.

In code

One call opens a capture.

curl, Node.js or Python: the same JSON, and the answer you get back.

$ curl -X POST https://api.tryvidimus.com/v1/capture-sessions \
  -H "Authorization: Bearer $TRYVIDIMUS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"external_reference":"booking_4471","party":"provider","stage":"pickup"}'
← 201 { "capture_url": "https://api.tryvidimus.com/v1/capture-sessions/…",
        "expires_at": "2026-09-28T18:30:00Z" }
→ webhook proof.sealed  prf_018f2e4a · booking_4471
Reliability

Built to be checked.

  • Public status pageThe API, the capture page, the verification page and the documentation, monitored from outside.Open the status page ↗
  • Free test modeThe full API with simulated timestamps. Nothing billed until you go live.
  • Test files deleted after 48 hoursLive proofs and their files are kept for 24 months, longer while a dispute is open.
  • A versioned APIEvery route lives under /v1, and its contract is the published OpenAPI schema.

Developer FAQ

Do I need an SDK?
No. The API is plain JSON over HTTPS and its schema is public: call it directly or generate a client. A typed TypeScript client is on npm.
What is the difference between test and live?
A test key (sk_test_) gives the full API with simulated timestamps: free, with no legal value, and files deleted after 48 hours. A live key (sk_live_) seals proofs with a qualified eIDAS timestamp, debited from your balance.
Does it work in a mobile app?
Yes. The capture page is a web page: your app opens it in a web view and gives it the camera. There is no native SDK to install.
Do the photos go through my servers?
No. They go straight from the phone to storage. Your server only creates the capture session and reads the proof.
How can someone check a proof without trusting you?
The verification page is public and needs no account. The verifier is open source (MIT) and published on npm: it recomputes the fingerprints and checks the timestamp on its own.
What is sealed?
Photos taken live on the capture page. Each one is fingerprinted, timestamped (qualified eIDAS) and signed (C2PA).

Start in test mode, for free.

Create an account, make a test key and seal your first proof today.

Create an account