K2anz Echosign

Name: Echosign API
Brand: Echosign
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone3 EndpointsREST

Install Jentic One Beta

Connect the Echosign to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Echosign, 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.

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 | sh

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 instance

Jentic 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 Echosign API.

CreateAgreement

GetAgreementStatus

UploadDocument

Query and filter Echosign records by parameters

GET STARTED

Start building with Echosign API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Echosign API for, with concrete tasks.

★ Developer Tools Operations

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

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.

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.

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

Key Endpoints

3 endpoints — api for secure.

METHOD

PATH

DESCRIPTION

POST

/api/rest/v6/agreements

CreateAgreement

GET

/api/rest/v6/agreements/{agreementId}

GetAgreementStatus

POST

/api/rest/v6/transientDocuments

UploadDocument

POST

/api/rest/v6/agreements

CreateAgreement

GET

/api/rest/v6/agreements/{agreementId}

GetAgreementStatus

POST

/api/rest/v6/transientDocuments

UploadDocument

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Echosign API through Jentic.

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.