Modusign API

Name: Modusign API
Brand: Modusign API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbasic, bearer31 EndpointsREST

For Agents

Send and track e-signature requests, apply templates, embed signing flows, and manage webhooks for the Korean Modusign signing platform.

Install Jentic One Beta

Connect the Modusign API to your agent

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

Send a signature request to one or more parties from an uploaded PDF

Send a signature request from a saved Modusign template with field values pre-filled

Cancel a pending signature request before all parties have signed

GET STARTED

Start building with Modusign API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Modusign API for, with concrete tasks.

★ Korean Contract Signing Workflow

Send Korean-language contracts to customers, employees, or counterparties for legally binding electronic signature. POST /documents creates a signing request from an uploaded PDF or merged file, GET /documents/{id} polls status, and POST /documents/{id}/remind nudges late signers. Most Korean SaaS teams ship a working signing flow in under a week using Basic auth with the account API key.

Upload a PDF NDA, create a signature request with two signers (legal@corp.kr and counterparty@vendor.kr), and return the document ID and signing URLs

Template-Driven HR Onboarding

Use saved Modusign templates for repeating HR documents — offer letters, NDAs, policy acknowledgements — and prefill signer-specific fields via POST /documents/template. The template ID is fixed but field values change per new hire, so HR systems can dispatch dozens of documents without re-uploading PDFs each time.

Send a Modusign template-based offer letter to candidate@example.kr with name, salary, and start date prefilled, and label the document 'onboarding-2026'

Embedded Signing in a Host App

Embed the signing experience inside a host web app so users never leave to sign. POST /embedded/drafts creates a draft and returns a short-lived embedded URL. The host app loads it in an iframe; on completion a webhook fires document.completed, which the host app uses to release downstream actions like contract activation.

Create an embedded draft from a template, return the embedded URL for the iframe, and set up a webhook to /our-app/sign-complete for document.completed events

Agent-Driven Contract Lifecycle via Jentic

Use a Jentic-connected agent to send signature requests, monitor status across documents, and remind late signers without bespoke integration code. The agent searches Jentic for the operation it needs, loads the schema, and calls Modusign with credentials drawn from the vault — a useful pattern for ops teams running thousands of contracts.

List all documents pending signature for more than 5 days and send a reminder via POST /documents/{id}/remind to each

Key Endpoints

31 endpoints — modusign is a korean electronic-signature platform whose api covers the full document signing lifecycle.

METHOD

PATH

DESCRIPTION

POST

/documents

Create a signature request from an uploaded file

POST

/documents/template

Create a signature request from a template

GET

/documents/{id}

Retrieve the current status of a document

POST

/documents/{id}/cancel

Cancel a pending signature request

POST

/documents/{id}/remind

Send a reminder to outstanding signers

POST

/embedded/drafts

Create an embedded signing draft

POST

/webhooks

Subscribe to document lifecycle webhooks

POST

/documents

Create a signature request from an uploaded file

POST

/documents/template

Create a signature request from a template

GET

/documents/{id}

Retrieve the current status of a document

POST

/documents/{id}/cancel

Cancel a pending signature request

POST

/documents/{id}/remind

Send a reminder to outstanding signers

Why Jentic?

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

Credential isolation

Modusign Basic-auth API keys and OAuth bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access — raw credentials never enter the agent context or appear in logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'send a contract for signing') and Jentic returns the matching Modusign operation with its body schema, so the agent calls the right endpoint without browsing Korean-language docs.

Time to first call

Direct Modusign integration including auth, template setup, webhook handling, and edge cases typically takes 3 to 5 days. Through Jentic: under one hour to search, load, and execute the first signing request.

FAQs

Specific to using Modusign API through Jentic.

What authentication does the Modusign API use?

Modusign supports HTTP Basic auth using the account email as username and the API key as password, or a Bearer OAuth access token for apps acting on behalf of a user. Both schemes target the same base URL https://api.modusign.co.kr. Through Jentic, both credential forms are stored encrypted in the MAXsystem vault and injected at execution time.

Can I send a signature request from a Modusign template?

Yes. POST /documents/template with the template ID and an array of participants and field values. The response includes the new document ID, status, and per-participant signing URLs. Templates are managed via GET and DELETE /templates and POST /templates.

What are the rate limits for the Modusign API?

The Modusign OpenAPI does not declare a numeric rate limit. The vendor's developer documentation indicates limits are applied per account at the platform level — agents should respect 429 responses, batch outgoing requests, and avoid tight polling on /documents/{id}; instead subscribe to webhooks for status changes.

How do I send a Korean e-signature request through Jentic?

Run pip install jentic, then search Jentic for 'send a contract for signing on Modusign'. Jentic returns the POST /documents operation with its body schema. Load the schema, pass the file ID and signer list, and execute. The Modusign API key is resolved from the vault and never enters the agent context.

Does Modusign support webhook notifications?

Yes. POST /webhooks registers a subscription URL and selected event types. Modusign delivers POST callbacks when documents move through statuses such as completed or cancelled. List existing subscriptions via GET /webhooks and remove them via DELETE /webhooks/{id}.

Can I embed the Modusign signing UI in my own app?

Yes. POST /embedded/drafts creates a draft and returns a short-lived embedded URL that the host application loads in an iframe. POST /embedded/drafts/template creates the same flow from a saved template. Combine with webhooks to act on document.completed events server-side.

Modusign API

Connect the Modusign API to your agent

Capabilities

Start building with Modusign API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs