SignEasy API
✓ Official Vendor SpecStorageObject Storagebearer, oauth220 EndpointsREST
For Agents
Programmatically fetch user, upload an original document. Covers 20 operations with bearer, oauth2 authentication.
Use for: I need to fetch user, I want to upload an original document, Search for fetch all originals, Find all fetch an original
Not supported: Does not handle payments, communications, or crm — use for storage and databases only.
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.
Install Jentic One Beta
Connect the SignEasy API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SignEasy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SignEasy API.
Fetch user
Upload an original document
Delete an original
Create or send an envelope
Monitor SignEasy API operational status and events
Use Cases
Patterns agents use SignEasy API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'fetch user', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
20 endpoints — signeasy api for electronic signature workflows including document upload, envelope creation, signing, templates, and embedded signing experiences.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
SignEasy API bearer, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'fetch user') and Jentic returns the matching SignEasy API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct SignEasy API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SignEasy API through Jentic.
What authentication does the SignEasy API use?
The SignEasy API uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED