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

# SignRequest API

SignRequest is a digital signature solution. This API allows you to create and manage document signing requests. The API exposes 35 endpoints secured with apiKey authentication.

## For AI agents

Programmatically retrieve a list of API tokens, retrieve a list of auditevents. Covers 35 operations with apiKey authentication.

## Scope

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

## Capabilities

- Retrieve a list of API tokens
- Create a Document Attachment
- Search documents
- Query and filter SignRequest API records by parameters
- Monitor SignRequest API operational status and events

## Use cases

### Developer Tools Operations

Use the SignRequest API to perform developer tools operations programmatically. The API provides 35 endpoints covering core functionality including retrieve a list of API tokens, retrieve a list of auditevents, create a document attachment.

Example prompt: Call GET /api-tokens to retrieve a list of API tokens

### Automated api-tokens Management

Automate api-tokens operations by combining multiple SignRequest API endpoints. Agents can retrieve a list of auditevents and then create a document attachment in a single workflow.

Example prompt: Call GET /audit-events to retrieve a list of auditevents, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SignRequest 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 'retrieve a list of API tokens', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api-tokens | Retrieve a list of API tokens |
| GET | /audit-events | Retrieve a list of AuditEvents |
| POST | /document-attachments | Create a Document Attachment |
| GET | /document-attachments | Retrieve a list of Document Attachments |
| GET | /document-attachments/{uuid} | Retrieve a Document Attachment |
| GET | /documents-search | Search documents |
| POST | /documents | Create a Document |
| GET | /documents | Retrieve a list of Documents |

## Key resources

- **api-tokens** — Operations related to api-tokens
- **audit-events** — Operations related to audit-events
- **document-attachments** — Operations related to document-attachments
- **documents** — Operations related to documents
- **documents-search** — Operations related to documents-search

## Why Jentic

- **Setup:** Wiring SignRequest by hand means putting its API key in the Authorization header, pointing calls at https://signrequest.com/api/v1, and tracking document and attachment uuids yourself. Through Jentic you install once, import SignRequest from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** SignRequest puts the attachment uuid in the URL path (/document-attachments/{uuid}), so a rule can pin your agent to one attachment: it can read that attachment and nothing else. You choose the operations it may call, so creating documents or attachments is not included unless you add it.
- **Credential handling:** Your SignRequest 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 'search documents' or 'list audit events', and Jentic returns the matching SignRequest 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 SignRequest API use?

The SignRequest 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 retrieve a list of API tokens with the SignRequest API?

Yes. Use the GET /api-tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SignRequest 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 retrieve a list of API tokens through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a list of API tokens'. Jentic returns the matching SignRequest API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The SignRequest API exposes 35 endpoints covering api-tokens, audit-events, document-attachments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SignRequest operations the agent may call and which stored credentials it may use. Since SignRequest puts the attachment uuid in the URL path (/document-attachments/{uuid}), a rule can pin the agent to a single attachment so it reads that one resource and nothing else. You choose the allowed operations, so write actions like creating documents (POST /documents) or attachments (POST /document-attachments) stay off limits unless you add them.