Go to main content
Certyneo
Public Postman collection

The Certyneo electronic signature API in Postman

Import the public Certyneo collection into Postman and test every REST v1 API endpoint — creating envelopes, sending, tracking status, webhooks — with request examples already filled in.

Free, public collection. A Certyneo API key is required to run requests.

Why use the Certyneo Postman collection

The collection is built for developers who want to explore the Certyneo API without reading the whole documentation before firing their first request.

  • Ready-to-run requests

    Every REST v1 endpoint is documented with a sample request and response, ready to run once you've filled in your API key.

  • Test environments

    A Postman environment variable holds your API key and the base URL, so switching between accounts or environments is easy.

  • Auto-generated documentation

    The collection's Postman documentation stays in sync with the Certyneo OpenAPI spec — no drift between what you test and what's in production.

  • Test without writing code

    Create an envelope, send it, and track its status directly from the Postman interface, before you even integrate the API into your application.

What the collection covers

An overview of the endpoint groups available in the public collection.

GroupWhat it contains
EnvelopesCreate, send, list, view and cancel a signature envelope.
DocumentsUpload a document or import it from a URL (sourceUrl), check its status.
SignersAdd recipients, set their signing order and level (SES/AES).
WebhooksCreate and manage subscriptions to signature events.
Bulk sendSend several envelopes in a single request for high-volume signature campaigns.

The collection is publicly readable: you can browse it without an account, but running requests requires a valid Certyneo API key.

Get started with the collection in 4 steps

Takes less than 5 minutes to fire your first request.

  1. 1

    Import the public collection

    From Postman, open the public Certyneo collection and click "Fork" or "Import" to copy it into your own workspace.

  2. 2

    Generate a Certyneo API key

    In your Certyneo dashboard, open Settings → API Keys and create a key dedicated to Postman.

  3. 3

    Set the environment variable

    Paste your API key into the collection's Postman environment variable, along with the API base URL.

  4. 4

    Send a first request

    Run the "Create an envelope" request and see the result directly in Postman.

Ready to explore the API?

Create a Certyneo account, generate an API key and start testing the Postman collection right away.

Security and best practices

Requests from the collection go through the same API as your production application: the same security rules apply.

  • All requests travel over HTTPS/TLS 1.2 minimum.
  • Each API key is limited to the permissions you grant it when creating it.
  • Use a dedicated test key for your Postman experiments, separate from your production key.
  • A compromised or unused API key can be revoked in one click from your Certyneo dashboard.

Frequently asked questions

Do I need a paid plan to use the Postman collection?

No. The collection is public and free. Your Certyneo plan's limits (number of envelopes, features) apply to the requests you run, just like any API usage.

Where do I find my API key?

In your Certyneo dashboard, under Settings → API Keys. Create a key dedicated to your Postman tests.

Is the collection up to date with the latest API version?

Yes, the collection is regenerated from the official Certyneo OpenAPI spec every time the REST v1 API evolves.

Can I test webhooks from Postman?

Yes, the collection includes endpoints to create and list your webhook subscriptions. To receive events locally, use an HTTP tunneling service while you test.

Does using the Postman collection cost anything?

No, only actual API usage (creating envelopes) is deducted from your plan, exactly like a regular API call.

Learn more

Test the Certyneo API in Postman

Public, free collection, kept in sync with our developer documentation.