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

# Signaturit API

Signaturit electronic signature API for creating and managing signature requests, certified emails, certified SMS, templates, brandings, team management, and webhook subscriptions. The API exposes 52 endpoints secured with bearer authentication.

## For AI agents

Programmatically count signature requests, create a new signature request. Covers 52 operations with bearer authentication.

## Scope

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

## Capabilities

- Count signature requests
- Create a new signature request
- List all signature requests
- Get a specific signature request
- Delete a signature request
- Send signature reminder email
- Cancel a signature request

## Use cases

### Communications Operations

Use the Signaturit API to perform communications operations programmatically. The API provides 52 endpoints covering core functionality including count signature requests, create a new signature request, list all signature requests.

Example prompt: Call GET `/signatures/count.json` to count signature requests

### Automated Account Management

Automate account operations by combining multiple Signaturit API endpoints. Agents can create a new signature request and then list all signature requests in a single workflow.

Example prompt: Call POST /signatures.json to create a new signature request, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Signaturit API 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 bearer tokens manually.

Example prompt: Search Jentic for 'count signature requests', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/signatures/count.json` | Count signature requests |
| POST | `/signatures.json` | Create a new signature request |
| GET | `/signatures.json` | List all signature requests |
| GET | `/signatures/{id}.json` | Get a specific signature request |
| DELETE | `/signatures/{id}.json` | Delete a signature request |
| POST | `/signatures/{id}/reminder.json` | Send signature reminder email |
| PATCH | `/signatures/{id}/cancel.json` | Cancel a signature request |
| GET | `/signatures/{id}/documents/{documentId}/download/signed` | Download signed document |

## Key resources

- **Account** — Operations related to Account
- **Brandings** — Operations related to Brandings
- **Certified Emails** — Operations related to Certified Emails
- **Certified Files** — Operations related to Certified Files
- **Certified SMS** — Operations related to Certified SMS

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 93 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/signaturit.com/signaturit/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 Signaturit by hand means learning its bearer token auth, choosing the live or sandbox host under https://api.signaturit.com/v3, and tracking signature request ids yourself. Through Jentic you install once, import Signaturit from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Signaturit puts the signature id in the URL path (`/signatures/{id}`), so a rule can pin your agent to one signature request: it can read it, download its signed documents, and send reminders and nothing else. You choose the operations it may call, so destructive ones like deleting or cancelling a request are not included unless you add them.
- **Credential handling:** Your Signaturit token 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 'count signature requests' or 'download a signed document', and Jentic returns the matching Signaturit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Signaturit API use?

The Signaturit API uses a Bearer token in the Authorization 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 count signature requests with the Signaturit API?

Yes. Use the GET `/signatures/count.json` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Signaturit API?

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 count signature requests through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'count signature requests'. Jentic returns the matching Signaturit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Signaturit API have?

The Signaturit API exposes 52 endpoints covering account, brandings, certified emails operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Signaturit operations and credentials the agent may use. Because Signaturit puts the signature id in the URL path (`/signatures/{id}`), you can pin the agent to a single signature request and grant only read, signed-document download, and reminder operations. Destructive calls like deleting or cancelling a request stay out of reach unless you explicitly add them.