canonical: https://jentic.com/apis/swaggerhub.k2anz/echosign

# K2anz Echosign

API for secure.au1.echosign.com. The API exposes 3 endpoints.

## For AI agents

Programmatically createagreement, getagreementstatus. Covers 3 operations.

## Scope

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

## Capabilities

- CreateAgreement
- GetAgreementStatus
- UploadDocument
- Query and filter Echosign records by parameters
- Monitor Echosign operational status and events

## Use cases

### Developer Tools Operations

Use the Echosign to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including createagreement, getagreementstatus, uploaddocument.

Example prompt: Call POST /api/rest/v6/agreements to createagreement

### Automated Web Management

Automate web operations by combining multiple Echosign endpoints. Agents can getagreementstatus and then uploaddocument in a single workflow.

Example prompt: Call GET /api/rest/v6/agreements/{agreementId} to getagreementstatus, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/rest/v6/agreements | CreateAgreement |
| GET | /api/rest/v6/agreements/{agreementId} | GetAgreementStatus |
| POST | /api/rest/v6/transientDocuments | UploadDocument |

## Key resources

- **Web** — Operations about Web

## Why Jentic

- **Setup:** Wiring Echosign by hand means pointing your client at secure.echosign.com, uploading transient documents, and threading agreement ids through the v6 REST flow yourself. Through Jentic you install once, import Echosign from the API Directory, and your agent calls it without you hand-building each request.
- **Permission scoping:** Echosign puts the agreement id in the URL path (/api/rest/v6/agreements/{agreementId}), so a rule can pin your agent to reading one agreement. You choose the operations it may call, so creating agreements or uploading transient documents is not included unless you add it.
- **Credential handling:** Any Echosign credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a signing agreement' or 'upload a document to sign', and Jentic returns the matching Echosign 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 Echosign use?

The Echosign uses no authentication. 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 createagreement with the Echosign?

Yes. Use the POST /api/rest/v6/agreements endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Echosign?

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 createagreement through Jentic?

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

### How many endpoints does the Echosign have?

The Echosign exposes 3 endpoints covering web operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Echosign operations and credentials the agent may use. You can allow only GetAgreementStatus so the agent reads a single agreement by the agreement id in its path, while leaving out CreateAgreement and UploadDocument unless you explicitly add them. This lets the operator pin the agent to read-only agreement lookups and keep document creation and uploads off limits.