Zined API is now live

Zined API is now live.

This release gives product, platform, and automation teams a new way to embed signing and document workflows into their own products, automations, and internal systems. If you want Zined to be part of your application flow rather than a separate manual step, this is the feature that opens that path.

The developer portal is live alongside the feature so your team has a clear implementation path from the first token to production integration.

What the Zined API enables

With the Zined API, teams can connect Zined more deeply into the systems they already run. That can include workflows such as:

• sending documents from your product instead of switching into a separate manual step
• embedding agreement and signature actions inside onboarding, sales, compliance, or operations flows
• managing templates and bulk sends programmatically for repeatable processes
• connecting document events to your internal systems and automation jobs

For teams already using Zined integrations, this adds a deeper layer: not just connecting storage providers, but integrating Zined directly into the way your product and workflows operate.

How to get started

If you want to go from account setup to first API call quickly, the cleanest path is:

1. Open Settings → API in the Zined app and create a Personal Access Token.
2. Store the token securely because the raw value is only displayed once.
3. Start with the Quick Start and Authentication guides.
4. Move into the API Reference when you are ready to implement production workflows.

How authentication works

Authorization: PAT znd_pat_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Zined's public API uses Personal Access Tokens for authentication. A few implementation details matter:

• PATs are scoped to your organization, so the org context is resolved from the token automatically in the common case
• the raw token value is shown only once at creation time, so it should be stored in your secrets manager immediately
• you can give each token a friendly name and optional expiry date
• usage metrics help you monitor which tokens are active and how they are being used

That makes PATs a practical fit for backend services, internal tooling, CI jobs, and workflow automations that need long-lived access without relying on short-lived session tokens.

What is available in the developer portal

The portal brings the supporting pieces of the release into one place:

• a quick start to help you authenticate, upload a document, and collect a signature faster
• a dedicated authentication guide for Personal Access Tokens
• a full API reference covering documents, templates, bulk send, contacts, users, workspaces, integrations, PAT management, and more

This is designed to reduce the gap between creating a token in Zined and shipping a working implementation in your own environment.

A new path for embedding Zined

This release is about making Zined easier to integrate into the products and workflows your team already owns.

The Zined API gives teams a clearer path from token creation to production implementation, while the developer portal makes that path easier to follow. If your team has been waiting for a more direct way to build on Zined, this is the moment to start.

Explore the Zined API docs, or request a demo if you want to talk through a more custom integration path.