canonical: https://jentic.com/apis/api.lleida.net/lleida-net # Lleida Click & Sign by Lleida.net API Jentic publishes the only available OpenAPI specification for Click & Sign by Lleida.net API, keeping it validated and agent-ready. Click & Sign is Lleida.net's electronic signature platform that lets businesses configure signature processes, send documents to one or many signatories, track signatory status, send reminders, and download signed files and audit evidence. The API exposes 17 POST endpoints covering configuration management, signature lifecycle operations, signatory tracking, file retrieval, and bulk batch signing. It is suited for legally binding contract signing workflows in Spain and the EU where qualified electronic evidence is required. ## For AI agents Configure and run electronic signature workflows on Lleida.net's Click & Sign platform: start signatures, track signatory status, send reminders, cancel processes, and download signed files and bulk signature batches. ## Scope Does not handle identity verification, KYC, or certified email delivery - use for electronic signature lifecycle management only. ## Capabilities - Create and update signature process configurations that define signatory flows, document templates, and notification rules - Start a single signature process and dispatch it to one or more named signatories - Poll signature status and individual signatory status to drive downstream business logic - Send reminders to signatories who have not yet completed a pending signature - Cancel an active signature process before signatories complete it - Download the signed document and the audit trail file once a signature has finished - Run bulk signature batches and validate batch payloads before dispatching to thousands of signatories ## Use cases ### Contract Signing for Sales Teams Automate sales contract signing by starting a Click & Sign signature process when a deal is closed, then polling for completion and storing the signed PDF in the CRM. The API handles signatory invitations, reminders, and the final audit-evidence file. Most sales teams integrate in 2 to 4 days using the configuration and start_signature endpoints. Example prompt: Start a Click & Sign signature process using configuration ID 'sales-contract-v1' for signatory email 'buyer@example.com' and the attached PDF, then poll get_signature_status until it reports completed and download the signed file. ### Bulk HR Document Distribution Send the same employment policy or annual disclosure document to hundreds of employees in one batch using bulk_start_signature. The API validates the batch first via bulk_validate, then runs the bulk job and exposes per-signatory progress through bulk_status. This replaces manual mail merges and individual signature requests for HR teams. Example prompt: Validate a bulk signature batch with 250 employees using bulk_validate, then call bulk_start_signature with the validated batch ID and poll bulk_status every 5 minutes until all signatures are complete. ### Compliance and Audit Evidence Retrieval Retrieve the complete signed file plus the cryptographic audit-evidence document for any past signature using get_file and get_file_list. Compliance teams use this to satisfy auditor requests for legally qualified electronic evidence under eIDAS without going through manual portal exports. Example prompt: Call get_file_list for signature ID 'SIG-2026-0412' to enumerate available files, then call get_file for each one and store them under the contract record. ### AI Agent Document Signing Workflow An AI agent triggered by a CRM event can call Click & Sign through Jentic to start a signature, monitor signatory progress, send reminders, and download the signed file once complete. Jentic's intent search returns the right endpoints from natural-language queries, so the agent does not need to read the Lleida.net API docs. Integration takes under an hour from sign-up to first signed document. Example prompt: Use Jentic to search for 'start an electronic signature', load the start_signature schema, and execute it with the contract PDF and signatory list, then monitor get_signature_status until completion. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /cs/v1/start_signature | Start a new signature process | | POST | /cs/v1/get_signature_status | Get the status of a signature process | | POST | /cs/v1/get_signatory_status | Get the status of a specific signatory | | POST | /cs/v1/send_reminder | Send a reminder to a signatory | | POST | /cs/v1/cancel_signature | Cancel an active signature process | | POST | /cs/v1/get_file | Download a signed file or audit evidence | | POST | /cs/v1/bulk_start_signature | Start a bulk signature batch | | POST | /cs/v1/bulk_status | Get the status of a bulk signature batch | ## Key resources - **Configuration** — Create, retrieve, list, and toggle signature process configurations that define signatory flows and document handling - **Signature** — Start, cancel, list, and check the status of individual signature processes - **Signatory** — Track per-signatory status, retrieve detailed signatory information, and send reminders - **File** — List and download signed documents and audit evidence files - **Bulk** — Validate, start, and monitor bulk signature batches across many signatories ## Why Jentic - **Setup:** Wiring the Click & Sign by Lleida.net API by hand means setting up its API key auth and coding your own calls across the start, status, and reminder signature endpoints. Through Jentic you install once, import the Click & Sign by Lleida.net API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Click & Sign signature ids travel in the request body rather than as ids in the URL path, so limit the agent to the operations it needs, such as start_signature and get_signature_status, and leave cancel_signature out of the allowed set. Every operation you grant is your explicit choice. - **Credential handling:** Your Lleida.net API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'start a signature request' or 'check a signatory's 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. ## Related APIs - **PandaDoc API** — Document and signature platform popular in North American sales workflows - **SignRequest API** — Lightweight European electronic signature service - **Signaturit API** — Spanish electronic signature and certified delivery platform ## FAQ ### Why is there no official OpenAPI spec for Click & Sign by Lleida.net 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 by Lleida.net 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 by Lleida.net API use? The API uses an API key sent on every POST request under the ApiKeyAuth scheme. Through Jentic, your Lleida.net key is stored encrypted in your Jentic One instance and never appears in agent context - agents receive scoped access only when executing a Click & Sign call. ### Can I run bulk signature batches with the Click & Sign by Lleida.net API? Yes. The API exposes /cs/v1/bulk_validate to check a batch payload, /cs/v1/bulk_start_signature to dispatch the batch, and /cs/v1/bulk_status to poll progress. This is the right endpoint set for sending the same document to hundreds or thousands of signatories in one job. ### What are the rate limits for the Click & Sign by Lleida.net API? Lleida.net does not publish public rate limits for Click & Sign. Limits are tied to your account plan - contact your Lleida.net account manager for the per-second and per-day caps that apply to your API key. ### How do I start a signature with the Click & Sign by Lleida.net API through Jentic? Run pip install jentic, then search for 'start an electronic signature' to surface the /cs/v1/start_signature operation. Load its input schema, populate the configuration ID, signatories, and document, and execute. Jentic returns the signature ID you then poll with /cs/v1/get_signature_status. ### Does the Click & Sign by Lleida.net API return audit evidence files? Yes. After a signature is complete, call /cs/v1/get_file_list with the signature ID to list available files, then /cs/v1/get_file to download the signed PDF and the audit-evidence document used for eIDAS-qualified electronic evidence. ### Can I limit what my agent is allowed to do with the Click & Sign by Lleida.net API? Yes. Because you run Jentic One yourself, your own rules decide which Click & Sign operations the agent may call, so you can grant only what a workflow needs, such as start_signature and get_signature_status, and leave cancel_signature out of the allowed set. Since signature IDs travel in the request body rather than the URL path, scoping is enforced at the operation level rather than by inspecting paths, and every operation you grant is your explicit choice. Your Lleida.net API key stays in your own instance and is supplied only when an allowed call runs, so the agent never receives credentials it can reuse elsewhere.