SignatureAPI

Name: SignatureAPI API
Brand: SignatureAPI
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey15 EndpointsREST

For Agents

Programmatically create an envelope, list envelopes. Covers 15 operations with apiKey authentication.

I need to an envelope, I want to envelopes, Search for an envelope, Find all an envelope

Install Jentic One Beta

Connect the SignatureAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SignatureAPI, 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.

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 | sh

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 instance

Jentic 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 SignatureAPI API.

Create an envelope

List envelopes

Retrieve an envelope

Update an envelope

GET STARTED

Start building with SignatureAPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SignatureAPI API for, with concrete tasks.

★ Developer Tools Operations

Use the SignatureAPI to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including create an envelope, list envelopes, retrieve an envelope.

Call POST /v1/envelopes to create an envelope

Automated Deliverables Management

Automate deliverables operations by combining multiple SignatureAPI endpoints. Agents can list envelopes and then retrieve an envelope in a single workflow.

Call GET /v1/envelopes to list envelopes, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SignatureAPI endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'create an envelope', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — electronic signature api for creating envelopes, managing documents, recipients, ceremonies, and deliverables.

METHOD

PATH

DESCRIPTION

POST

/v1/envelopes

Create an envelope

GET

/v1/envelopes

List envelopes

GET

/v1/envelopes/{envelope_id}

Retrieve an envelope

PATCH

/v1/envelopes/{envelope_id}

Update an envelope

DELETE

/v1/envelopes/{envelope_id}

Delete an envelope

POST

/v1/envelopes/{envelope_id}/cancel

Cancel an envelope

GET

/v1/envelopes/{envelope_id}/events

List envelope events

POST

/v1/envelopes/{envelope_id}/deliverables

Create a deliverable

POST

/v1/envelopes

Create an envelope

GET

/v1/envelopes

List envelopes

GET

/v1/envelopes/{envelope_id}

Retrieve an envelope

PATCH

/v1/envelopes/{envelope_id}

Update an envelope

DELETE

/v1/envelopes/{envelope_id}

Delete an envelope

POST

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

SignatureAPI apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create an envelope') and Jentic returns the matching SignatureAPI operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SignatureAPI integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using SignatureAPI API through Jentic.

What authentication does the SignatureAPI use?

The SignatureAPI uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create an envelope with the SignatureAPI?

Yes. Use the POST /v1/envelopes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the SignatureAPI?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create an envelope through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create an envelope'. Jentic returns the matching SignatureAPI operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the SignatureAPI have?

The SignatureAPI exposes 15 endpoints covering deliverables, envelopes, recipients operations.