SignRequest API

Name: SignRequest API API
Brand: SignRequest API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey35 EndpointsREST

For Agents

Programmatically retrieve a list of api tokens, retrieve a list of auditevents. Covers 35 operations with apiKey authentication.

Quickstart

Get started with SignRequest API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"retrieve a list of api tokens"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with SignRequest API API.

Retrieve a list of API tokens

Create a Document Attachment

Search documents

Query and filter SignRequest API records by parameters

Monitor SignRequest API operational status and events

GET STARTED

Start building with SignRequest API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use SignRequest API API for, with concrete tasks.

★ Developer Tools Operations

Use the SignRequest API to perform developer tools operations programmatically. The API provides 35 endpoints covering core functionality including retrieve a list of api tokens, retrieve a list of auditevents, create a document attachment.

Call GET /api-tokens to retrieve a list of api tokens

Automated api-tokens Management

Automate api-tokens operations by combining multiple SignRequest API endpoints. Agents can retrieve a list of auditevents and then create a document attachment in a single workflow.

Call GET /audit-events to retrieve a list of auditevents, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'retrieve a list of api tokens', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

35 endpoints — signrequest is a digital signature solution.

METHOD

PATH

DESCRIPTION

GET

/api-tokens

Retrieve a list of API tokens

GET

/audit-events

Retrieve a list of AuditEvents

POST

/document-attachments

Create a Document Attachment

GET

/document-attachments

Retrieve a list of Document Attachments

GET

/document-attachments/{uuid}

Retrieve a Document Attachment

GET

/documents-search

Search documents

POST

/documents

Create a Document

GET

/documents

Retrieve a list of Documents

GET

/api-tokens

Retrieve a list of API tokens

GET

/audit-events

Retrieve a list of AuditEvents

POST

/document-attachments

Create a Document Attachment

GET

/document-attachments

Retrieve a list of Document Attachments

GET

/document-attachments/{uuid}

Retrieve a Document Attachment

Why though Jentic?

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

Credential isolation

SignRequest API apiKey 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., 'retrieve a list of api tokens') and Jentic returns the matching SignRequest API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct SignRequest 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.

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 SignRequest API API through Jentic.

What authentication does the SignRequest API use?

The SignRequest API uses an API key passed 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 retrieve a list of api tokens with the SignRequest API?

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

What are the rate limits for the SignRequest 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 retrieve a list of api tokens through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'retrieve a list of api tokens'. Jentic returns the matching SignRequest API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the SignRequest API have?

The SignRequest API exposes 35 endpoints covering api-tokens, audit-events, document-attachments operations.