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

# Signaturely API

Electronic signature API for creating, sending, and managing documents and templates. The API exposes 22 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create document from template, bulk send documents from template. Covers 22 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create document from template
- Bulk send documents from template
- List recent documents
- Get document signers
- Rename a document

## Use cases

### Developer Tools Operations

Use the Signaturely API to perform developer tools operations programmatically. The API provides 22 endpoints covering core functionality including create document from template, bulk send documents from template, list recent documents.

Example prompt: Call POST `/document_sign/api/request_by_template` to create document from template

### Automated Add Teammates Management

Automate add teammates operations by combining multiple Signaturely API endpoints. Agents can bulk send documents from template and then list recent documents in a single workflow.

Example prompt: Call POST `/document_sign/api/bulk_send` to bulk send documents from template, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Signaturely 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create document from template', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/document_sign/api/request_by_template` | Create document from template |
| POST | `/document_sign/api/bulk_send` | Bulk send documents from template |
| GET | `/documents` | List recent documents |
| GET | `/documents/api/templates` | List available templates |
| GET | `/documents/{documentId}/signers` | Get document signers |
| GET | `/documents/{id}/activities` | Get document activity log |
| PATCH | `/documents/{id}/rename` | Rename a document |
| PATCH | `/documents/{documentId}/revert` | Revert a document |

## Key resources

- **Add Teammates** — Operations for add teammates
- **Api Integrations** — Operations for api integrations
- **Document_Sign** — Operations for document_sign
- **Documents** — Operations for documents
- **Hooks** — Operations for hooks

## 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:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/signaturely.com/signaturely/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 Signaturely by hand means putting its API key in the Authorization header, pointing calls at https://api.signaturely.com/api/v1, and tracking document and template ids yourself. Through Jentic you install once, import Signaturely from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Signaturely puts the document id in the URL path (`/documents/{documentId}`), so a rule can pin your agent to one document: it can read that document's signers and activities and nothing else. You choose the operations it may call, so writes like renaming or reverting a document are not included unless you add them.
- **Credential handling:** Your Signaturely API 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 a document from a template' or 'list document signers', and Jentic returns the matching Signaturely 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 Signaturely API use?

The Signaturely API uses an API key passed 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 create document from template with the Signaturely API?

Yes. Use the POST `/document_sign/api/request_by_template` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Signaturely 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 create document from template through Jentic?

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

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

The Signaturely API exposes 22 endpoints covering add teammates, API integrations, document_sign operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Signaturely operations and credentials the agent may use. Because Signaturely puts the document id in the URL path (`/documents/{documentId}`), a rule can pin the agent to a single document and let it read only that document's signers and activity log. You choose the operations it may call, so write actions like renaming (PATCH `/documents/{id}/rename`) or reverting a document are not available unless you explicitly add them.