Blueink API v2
★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbearer44 EndpointsREST
For Agents
Send documents for electronic signature, track signer status, and download signed bundles and certificates of evidence through Blueink.
Use for: Send a document for signature with Blueink, Check the signing status of a Blueink bundle, Send a reminder to a Blueink signer, Cancel a Blueink signature bundle
Not supported: Does not store long-term document archives, generate document content, or process payments — use for sending, tracking, and downloading electronic signature bundles only.
Jentic publishes the only available OpenAPI specification for Blueink API v2, keeping it validated and agent-ready. Blueink is an electronic signature platform, and the v2 API exposes signing bundles, signer packets, reusable templates, person directory entries, and webhook subscriptions. Senders create a bundle of documents, attach packets for each signer, and track signing events through to completion-of-evidence reports. Authentication uses a private API token sent as a Bearer header, and the base URL is https://api.blueink.com/api/v2.
Install Jentic One Beta
Connect the Blueink API v2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blueink API v2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Blueink API v2 API.
Create a signing bundle from raw files or a saved envelope template
Track signer progress through bundle event timelines and packet status
Generate embedded signing URLs for in-app signature flows
Send reminder emails to signers who have not yet completed their packet
Cancel an in-flight bundle before all signers have completed
Manage a directory of recurring signers in the persons resource
Configure webhooks to receive bundle and packet status events with custom headers
Use Cases
Patterns agents use Blueink API v2 API for, with concrete tasks.
★ Contract signing for sales close
Send a sales contract for electronic signature when a deal closes in the CRM. POST /bundles/ uploads the document and signer packets in a single call, returning a bundleSlug used to track progress. Subsequent GET /bundles/{bundleSlug}/events/ reveals each viewed, signed, and declined event, and GET /bundles/{bundleSlug}/files/ returns the executed PDF and certificate of evidence after completion.
Call POST /bundles/ with a contract PDF and a signer packet for the prospect's email, then poll GET /bundles/{bundleSlug}/events/ until status is 'complete'.
Embedded signing in a customer portal
Embed the Blueink signing experience inside the sender's own application instead of redirecting to Blueink's hosted UI. Create the bundle, then call POST /packets/{packetId}/embed_url/ for each signer to receive a short-lived URL you load into an iframe or webview. Useful for SaaS onboarding, financial services portals, and any flow where staying on-brand matters.
Call POST /packets/{packetId}/embed_url/ for an existing packet and return the signing URL for embedding.
Template-driven recurring agreements
Use saved Blueink envelope templates to issue NDAs, SOWs, or HR onboarding documents repeatedly with consistent fields and routing. POST /bundles/create_from_envelope_template/ creates a new bundle from a template ID, with signer details merged in at send time. GET /templates/ and GET /templates/{templateId}/ enumerate available templates and their fields.
Call POST /bundles/create_from_envelope_template/ with a template ID and signer info to issue a new NDA for a vendor onboarding.
Webhook-driven completion automation
Trigger downstream workflows when Blueink documents are fully signed by configuring webhooks. POST /webhooks/ creates a subscription, and POST /webhooks/headers/ attaches custom HTTP headers (e.g. for HMAC verification). When a bundle completes, the webhook fires with bundle and packet details so the receiving system can store the executed PDF and update the originating record.
Call POST /webhooks/ with a target URL and event filter for bundle.completed, then POST /webhooks/headers/ to add an Authorization header for the receiver.
AI agent contract sending assistant
Let an AI agent draft, send, and chase contracts on a user's behalf. The agent searches Jentic for the right Blueink operation by intent, loads the schema, and executes with the API token held in the Jentic vault. Suitable for sales copilots, legal-ops automation, and HR onboarding agents that need to put documents in front of signers without manual UI work.
Search Jentic for 'send a document for signature', load the schema for POST /bundles/, and execute it with a contract PDF and signer email for an embedded signing flow.
Key Endpoints
44 endpoints — jentic publishes the only available openapi specification for blueink api v2, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/bundles/
Create a new signing bundle
POST
/bundles/create_from_envelope_template/
Create a bundle from a saved template
GET
/bundles/{bundleSlug}/events/
Return the event timeline for a bundle
PUT
/bundles/{bundleSlug}/cancel/
Cancel an in-flight bundle
POST
/packets/{packetId}/embed_url/
Generate an embedded signing URL
PUT
/packets/{packetId}/remind/
Send a reminder to a signer
GET
/packets/{packetId}/coe/
Download the certificate of evidence
POST
/webhooks/
Create a webhook subscription
POST
/bundles/
Create a new signing bundle
POST
/bundles/create_from_envelope_template/
Create a bundle from a saved template
GET
/bundles/{bundleSlug}/events/
Return the event timeline for a bundle
PUT
/bundles/{bundleSlug}/cancel/
Cancel an in-flight bundle
POST
/packets/{packetId}/embed_url/
Generate an embedded signing URL
PUT
/packets/{packetId}/remind/
Send a reminder to a signer
GET
/packets/{packetId}/coe/
Download the certificate of evidence
POST
/webhooks/
Create a webhook subscription
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Blueink Bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw API token never enters agent context, and per-environment tokens (sandbox vs production) are isolated under separate credentials.
Intent-based discovery
Agents search by intent (e.g. 'send a document for signature' or 'send a signing reminder') and Jentic returns the matching Blueink operation across the 44 endpoints with its input schema, so the agent can call the right path without browsing the docs.
Time to first call
Direct integration: 1-2 days for bundle creation, packet routing, embed URL handling, and webhook signature verification. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Blueink API v2 API through Jentic.
Why is there no official OpenAPI spec for Blueink API v2?
Blueink publishes a Postman collection and HTML reference but does not distribute a maintained OpenAPI 3 file. Jentic generates and maintains this spec so AI agents and developers can call the Blueink API via standard tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Blueink API use?
Blueink uses a private API token sent as a Bearer credential in the Authorization header (Authorization: Token <api-key>). Tokens are issued from the Blueink dashboard. Through Jentic, the token is stored in the encrypted vault and injected at execution time, so the agent never handles the raw value.
Can I send a document for signature through this API?
Yes. POST /bundles/ accepts the documents, signer packets (each with email, name, and signature fields), and routing rules in a single call, returning a bundleSlug used to track the bundle. Files can be uploaded inline as base64 or referenced by URL.
What are the rate limits for the Blueink API?
Blueink applies per-account rate limits that are not enumerated in the spec. The published guidance is to keep request volume under roughly 60 requests per minute per token; HTTP 429 responses include a Retry-After header. Higher throughput is available on enterprise plans by request.
How do I track signer status through Jentic?
Search Jentic for 'check the signing status of a bundle', load the schema for GET /bundles/{bundleSlug}/events/, and execute it with the bundleSlug. Install with pip install jentic and call await client.execute(ExecutionRequest(...)). The response lists viewed, signed, declined, and completed events per signer.
Does Blueink support embedded signing?
Yes. After creating a bundle, call POST /packets/{packetId}/embed_url/ for each signer to receive a short-lived signing URL. Load the URL in an iframe or webview to keep signers inside your own application.
Is the Blueink API free?
Blueink offers tiered pricing — API access is included on paid plans, and a free trial is available for evaluation. Per-document pricing depends on the plan; volume discounts apply on annual contracts.
GET STARTED