Signaturit API

Name: Signaturit API
Brand: Signaturit API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail Deliverybearer52 EndpointsREST

For Agents

Programmatically count signature requests, create a new signature request. Covers 52 operations with bearer authentication.

Install Jentic One Beta

Connect the Signaturit API to your agent

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

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 Signaturit API.

Count signature requests

Create a new signature request

List all signature requests

Get a specific signature request

GET STARTED

Start building with Signaturit API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Signaturit API for, with concrete tasks.

★ Communications Operations

Use the Signaturit API to perform communications operations programmatically. The API provides 52 endpoints covering core functionality including count signature requests, create a new signature request, list all signature requests.

Call GET /signatures/count.json to count signature requests

Automated Account Management

Automate account operations by combining multiple Signaturit API endpoints. Agents can create a new signature request and then list all signature requests in a single workflow.

Call POST /signatures.json to create a new signature request, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'count signature requests', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

52 endpoints — signaturit electronic signature api for creating and managing signature requests, certified emails, certified sms, templates, brandings, team management, and webhook subscriptions.

METHOD

PATH

DESCRIPTION

GET

/signatures/count.json

Count signature requests

POST

/signatures.json

Create a new signature request

GET

/signatures.json

List all signature requests

GET

/signatures/{id}.json

Get a specific signature request

DELETE

/signatures/{id}.json

Delete a signature request

POST

/signatures/{id}/reminder.json

Send signature reminder email

PATCH

/signatures/{id}/cancel.json

Cancel a signature request

GET

/signatures/{id}/documents/{documentId}/download/signed

Download signed document

GET

/signatures/count.json

Count signature requests

POST

/signatures.json

Create a new signature request

GET

/signatures.json

List all signature requests

GET

/signatures/{id}.json

Get a specific signature request

DELETE

/signatures/{id}.json

Delete a signature request

Why Jentic?

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

Credential isolation

Signaturit API bearer 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., 'count signature requests') and Jentic returns the matching Signaturit API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Signaturit API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Signaturit API through Jentic.

What authentication does the Signaturit API use?

The Signaturit API uses a Bearer token in the Authorization header. 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 count signature requests with the Signaturit API?

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

What are the rate limits for the Signaturit 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 count signature requests through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'count signature requests'. Jentic returns the matching Signaturit API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Signaturit API have?

The Signaturit API exposes 52 endpoints covering account, brandings, certified emails operations.

Signaturit API

Connect the Signaturit API to your agent

Capabilities

Start building with Signaturit API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs