Lleida Click & Sign API

Name: Click & Sign API
Brand: Click & Sign API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity VerificationapiKey17 EndpointsREST

For Agents

Configure digital signature processes and send documents for legally binding electronic signature, then track signatory status and retrieve signed files via the Lleida.net Click & Sign API.

Install Jentic One Beta

Connect the Click & Sign API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Click & Sign 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Flleida.net%2Flleida-net" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flleida.net%2Flleida-net" | 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 Click & Sign API.

Configure reusable signature processes with documents, signing order, and notification channels

Launch single signature requests and track each signatory's status through completion

Submit bulk signature jobs that fan out the same configuration across many recipients

GET STARTED

Start building with Click & Sign API

Explore with Jentic One

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Click & Sign API, keeping it validated and agent-ready. Click & Sign by Lleida.net is a digital signature platform for legally binding electronic signature workflows. The API lets developers configure signature processes, launch single or bulk signature requests, track signatory status, send reminders, cancel pending signatures, and retrieve signed documents. It is built around a process-and-signatory model where each configuration defines the documents, signing flow, and notification channels for a class of agreements.

Use Cases

Patterns agents use Click & Sign API for, with concrete tasks.

★ Sales Contract E-Signature

Sales teams need a documented, legally binding signature on a contract before booking revenue. Click & Sign lets you start a signature with one or more signatories, route email or SMS notifications, track each signatory's status, send reminders, and pull the final signed document with audit evidence. The API is process-driven, so the same configuration can be reused across many contracts.

Call /start_signature with a saved configuration, the contract PDF, and the customer's email and phone, then poll /get_signature_status until completion.

HR Bulk Document Signing

HR teams send the same policy or onboarding pack to many employees at once. Click & Sign supports bulk validation of recipient details and bulk signature launches, so a single API call can dispatch hundreds of personalised signature requests under one configuration. Status for each recipient is exposed individually for compliance reporting.

Run /bulk_validate on a CSV of employee contacts, then /bulk_start_signature with the validated list against an HR policy configuration, and check /bulk_status hourly.

AI Agent Document Signing

An AI agent that drafts an agreement and needs to send it for signature can use Jentic to discover the right Click & Sign operation, launch the signature request, and surface progress to the user without holding raw API credentials. The agent never sees the API key, and the signature workflow is reduced to a search, load, and execute pattern.

Use Jentic to call /start_signature with a configured process ID and recipient details, then return the signature URL and tracking ID to the user.

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for click & sign api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/start_signature

Launch a single signature request

POST

/get_signature_status

Check the status of a signature process

POST

/send_reminder

Remind a pending signatory

POST

/cancel_signature

Cancel an in-progress signature

POST

/bulk_start_signature

Launch a bulk signature run

POST

/get_file

Retrieve a signed document

POST

/start_signature

Launch a single signature request

POST

/get_signature_status

Check the status of a signature process

POST

/send_reminder

Remind a pending signatory

POST

/cancel_signature

Cancel an in-progress signature

POST

/bulk_start_signature

Launch a bulk signature run

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Click & Sign API by hand means setting up its X-API-Key header auth, targeting api.lleida.net, and handling retries yourself across the signature workflow. Through Jentic you install once, import the Click & Sign API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Click & Sign identifies the signature in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as POST /start_signature or POST /get_signature_status. You choose the operations it may call, so POST /cancel_signature is not included unless you add it.

Credential isolation

Your Lleida.net X-API-Key is stored once, encrypted, by your own Jentic One instance and injected as the request header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a contract for electronic signature' or 'check signature status', and Jentic returns the matching Click & Sign operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Click & Sign API through Jentic.

Why is there no official OpenAPI spec for Click & Sign API?

Lleida.net does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Click & Sign API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Click & Sign API use?

The API requires an API key passed in the X-API-Key header on every request. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the raw value never reaches the agent's context.

Can I send a single signature request without setting up a configuration first?

No. Click & Sign is process-driven: configurations defined via /set_config hold the document templates, signing order, and notification channels, and /start_signature references a saved configuration plus the recipient details for each request.

What are the rate limits for the Click & Sign API?

Rate limits are not declared in the spec. Lleida.net applies per-account quotas at the contract level for bulk signing in particular; check your contract or contact the vendor for your tier.

How do I send a contract for signature through Jentic?

Search Jentic for 'send contract for electronic signature'. Jentic returns the /start_signature operation. Load the schema, supply your saved configuration ID and the recipient's email or phone, and execute. Poll /get_signature_status to track completion.

Can I run a bulk signature campaign with this API?

Yes. Use /bulk_validate to clean a recipient list, then /bulk_start_signature to launch the campaign. /bulk_status returns per-recipient progress, and /get_file retrieves each signed document once complete.

Can I limit what my agent is allowed to do with the Click & Sign API?

Yes. Because Jentic One is self-hosted, you set the rules on your own instance and decide which Click & Sign operations your agent may call. Since this API identifies the signature in the request body rather than in the URL path, you scope by operation, granting only what the agent needs, such as POST /start_signature or POST /get_signature_status. Operations like POST /cancel_signature are not available to the agent unless you add them, and the encrypted API key is injected at execution time so it never enters the agent's context.

Lleida Click & Sign API

Connect the Click & Sign API to your agent

Capabilities

Start building with Click & Sign API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs