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

# SignEasy API

SignEasy API for electronic signature workflows including document upload, envelope creation, signing, templates, and embedded signing experiences. The API exposes 20 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically fetch user, upload an original document. Covers 20 operations with bearer, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Fetch user
- Upload an original document
- Delete an original
- Create or send an envelope
- Monitor SignEasy API operational status and events

## Use cases

### Storage and Databases Operations

Use the SignEasy API to perform storage operations programmatically. The API provides 20 endpoints covering core functionality including fetch user, upload an original document, fetch all originals.

Example prompt: Call GET /user to fetch user

### Automated Embedded_Sending_Url Management

Automate embedded_sending_url operations by combining multiple SignEasy API endpoints. Agents can upload an original document and then fetch all originals in a single workflow.

Example prompt: Call POST /originals to upload an original document, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SignEasy 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, oauth2 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/user` | Fetch user |
| POST | `/originals` | Upload an original document |
| GET | `/originals` | Fetch all originals |
| GET | `/originals/{id}` | Fetch an original |
| DELETE | `/originals/{id}` | Delete an original |
| POST | `/envelopes` | Create or send an envelope |
| GET | `/envelopes` | Fetch all envelopes |
| GET | `/envelopes/{id}` | Fetch an envelope |

## Key resources

- **Embedded_Sending_Url** — Operations for embedded_sending_url
- **Embedded_Signing_Url** — Operations for embedded_signing_url
- **Envelopes** — Operations for envelopes
- **Originals** — Operations for originals
- **Signed_Envelopes** — Operations for signed_envelopes

## 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:** 71 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 77 / 100
- **View full report:** https://jentic.com/apis/signeasy.com/signeasy/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 SignEasy by hand means choosing between bearer token and OAuth2 authorization-code auth, pointing calls at https://api.signeasy.com/v3, and tracking original and envelope ids yourself. Through Jentic you install once, import SignEasy from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** SignEasy puts the original and envelope ids in the URL path (`/envelopes/{id}`), so a rule can pin your agent to one envelope: it can read that envelope and nothing else. You choose the operations it may call, so destructive ones like deleting an original are not included unless you add them.
- **Credential handling:** Your SignEasy credential 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 'upload an original document' or 'get an envelope', and Jentic returns the matching SignEasy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the SignEasy API use?

The SignEasy API uses bearer, oauth2 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 fetch user with the SignEasy API?

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

### What are the rate limits for the SignEasy 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 fetch user through Jentic?

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

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

The SignEasy API exposes 20 endpoints covering embedded_sending_url, embedded_signing_url, envelopes operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which SignEasy operations and credentials the agent may use. Because SignEasy puts original and envelope ids in the URL path, such as `/envelopes/{id}`, you can pin the agent to a single envelope so it can read that one and nothing else. You also choose the operations it may call, so a destructive call like DELETE `/originals/{id}` is excluded unless you explicitly add it.