canonical: https://jentic.com/apis/signatureapi.com/signatureapi

# SignatureAPI

Electronic signature API for creating envelopes, managing documents, recipients, ceremonies, and deliverables. The API exposes 15 endpoints secured with apiKey authentication.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create an envelope
- List envelopes
- Retrieve an envelope
- Update an envelope
- Delete an envelope
- Cancel an envelope

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Deliverables** — Operations for deliverables
- **Envelopes** — Operations for envelopes
- **Recipients** — Operations for recipients
- **Uploads** — Operations for uploads

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 75 / 100
- **Maturity:** AI-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 82 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/signatureapi.com/signatureapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring SignatureAPI by hand means sending its X-API-Key header, pointing calls at https://api.signatureapi.com, and tracking envelope ids and their events yourself. Through Jentic you install once, import SignatureAPI from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** SignatureAPI puts the envelope id in the URL path (`/v1/envelopes/{envelope_id}`), so a rule can pin your agent to one envelope: it can read that envelope, its events, and its deliverables and nothing else. You choose the operations it may call, so destructive ones like deleting or cancelling an envelope are not included unless you add them.
- **Credential handling:** Your SignatureAPI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an envelope' or 'get envelope events', and Jentic returns the matching SignatureAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the SignatureAPI?

Yes. Because you run Jentic One yourself and set the rules, you decide which SignatureAPI operations and credentials your agent may use. Since the envelope id sits in the URL path (`/v1/envelopes/{envelope_id}`), a rule can pin the agent to a single envelope so it only reads that envelope, its events, and its deliverables. Destructive operations such as deleting or cancelling an envelope stay off limits unless you explicitly allow them.