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

# Signwell Resources and endpoints

When I started SignWell in 2019, I saw there was a need for an alternative to the hard-to-use and expensive e-signature software already out there. Documents can be complicated enough, but getting a document signed shouldn't be complicated too. At SignWell, we pride ourselves not only on the ease and affordability of our e-signature process but also on our personalized and industry-leading custome. The API exposes 23 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send reminder, get bulk send. Covers 23 operations with apiKey authentication.

## Scope

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

## Capabilities

- Send Reminder
- Get Bulk Send
- Create Bulk Send
- List Bulk Sendings
- Validate Bulk Send CSV

## Use cases

### CRM Operations

Use the Resources and endpoints to perform crm operations programmatically. The API provides 23 endpoints covering core functionality including send reminder, get bulk send, create bulk send.

Example prompt: Call POST /api/v1/documents/{id}/remind to send reminder

### Automated Document Management

Automate document operations by combining multiple Resources and endpoints endpoints. Agents can get bulk send and then create bulk send in a single workflow.

Example prompt: Call GET /api/v1/bulk_sends/{id} to get bulk send, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Resources and endpoints 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 'send reminder', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v1/documents/{id}/remind | Send Reminder |
| GET | /api/v1/bulk_sends/{id} | Get Bulk Send |
| POST | /api/v1/bulk_sends | Create Bulk Send |
| GET | /api/v1/bulk_sends | List Bulk Sendings |
| GET | /api/v1/bulk_sends/csv_template | Get Bulk Send CSV Template |
| POST | /api/v1/bulk_sends/validate_csv | Validate Bulk Send CSV |
| GET | /api/v1/bulk_sends/{id}/documents | Get Bulk Send Documents |
| GET | /api/v1/documents/{id} | Get Document |

## Key resources

- **Document** — Operations related to Document
- **Bulk Send** — Operations related to Bulk Send
- **Template** — Operations related to Template
- **Webhooks** — Operations related to Webhooks
- **API Application** — Operations related to API Application

## Why Jentic

- **Setup:** Wiring SignWell by hand means sending its API-key request header, resolving your configured host, and tracking document and bulk-send ids yourself. Through Jentic you install once, import SignWell from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** SignWell puts the document and bulk-send ids in the URL path (/api/v1/documents/{id}), so a rule can pin your agent to one document or bulk send: it can read it and send reminders and nothing else. You choose the operations it may call, so creating a bulk send is not included unless you add it.
- **Credential handling:** Your SignWell 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 'send a reminder' or 'get a bulk send status', and Jentic returns the matching SignWell operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Resources and endpoints use?

The Resources and endpoints 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 send reminder with the Resources and endpoints?

Yes. Use the POST /api/v1/documents/{id}/remind endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Resources and endpoints?

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 send reminder through Jentic?

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

### How many endpoints does the Resources and endpoints have?

The Resources and endpoints exposes 23 endpoints covering document, bulk send, template operations.

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

Yes. Because you run Jentic One yourself, you decide which SignWell operations your agent may call and which credentials it may use. SignWell puts document and bulk-send ids in the URL path, such as /api/v1/documents/{id}, so your rules can pin the agent to a single document or bulk send and allow only reading it and sending reminders. Since you choose the permitted operations, an action like creating a bulk send through POST /api/v1/bulk_sends stays blocked until you explicitly grant it.