API

Automate certification in your own workflow.

With the rightsguardian API, your scripts, your exports or your content management system certify every version in your rightsguardian account, alongside the rest of your work.

In development · Early access open

How it works

Fingerprint, certificate, done.

  1. 1

    Compute the fingerprint

    In your system, with a standard algorithm.

  2. 2

    Send it to the API

    With your rightsguardian account. Only the fingerprint, never the content.

  3. 3

    Store the certificate

    Next to your content, wherever you choose.

  4. 4

    All in your history

    The certificate joins your work's history, alongside your other tools.

What for

What the add-ins don't cover.

Exports

Every PDF, ePub or render your workflow produces, certified on the way out.

Design and code

Your scripts and repositories certify every delivery.

Publishers and small teams

Connect your content management system and certify every submission and every final version.

Why rightsguardian

Your account, your history, one bill.

One history

What you certify through the API goes to the same account and the same history of each work as Word, Google Docs or the desktop app.

No infrastructure

You don't have to become a certificate issuer: your rightsguardian account is all you need.

Stateless by design

Your content stays in your system.

The API receives the fingerprint and returns the certificate. It doesn't store your content or your history: those stay with you.

  • Only the fingerprint travels
  • Certificates are stored wherever you choose
  • Verifiable with open tools, without depending on us

Be among the first to certify your creative process.

Join early access. We'll let you know as soon as your integration is ready, so you can try it before anyone else.

Get early access

No commitment. Unsubscribe at any time.