JuriSign API
Documented, versioned REST API (OpenAPI 3.0.3, 46 operations across 8 tags) for eIDAS SES electronic signatures: documents, sign requests, templates, bulk campaigns, public forms, account credits, webhooks and authentication. Bearer token auth with five restrictable scopes, an Idempotency-Key on sign-request creation, page-number pagination, and a free sandbox token flow that neutralises real delivery and billing while still firing webhooks.
This API exposes 46 operations across 31 paths, organized into 8 resource areas, and defines 15 schemas. It is described by OpenAPI 3.0.3, at version 3.24.1.
Requests are made against a single base URL, https://jurisign.fr/api/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
JuriSign API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
bearerAuth— Obtain a token via POST /auth/token, then pass it as: Authorization: Bearer {token}
Paths & Operations 46
Across 31 paths, the API surfaces 46 operations — 7 DELETE, 20 GET, 16 POST, 3 PUT. They span 8 resource areas: Authentication, Account, Templates, Bulk, Public Forms, Documents, Sign Requests, Webhooks. Each is listed below with its method, path, parameters, and response codes.
Obtain and revoke API tokens
Credit balance and plan
Reusable sign request templates
Merge templates and bulk campaigns (one individualised request per recipient)
Shareable links: each respondent signs their own generated request, no account needed
Upload and manage PDF documents
Create, send, and track signature requests
Manage webhook endpoints for event notifications
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are SignRequest (16 properties), Template (14 properties), CreateSignRequestInput (11 properties), BulkCampaign (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
This is an independent, third-party profile of JuriSign API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.