JuriSign website screenshot

JuriSign

eIDAS electronic signature API developed in France by PCFrance and hosted in Europe. JuriSign issues Simple Electronic Signatures (SES) under eIDAS Regulation (EU) No 910/2014 only -- not advanced (AdES) and not qualified (QES). The 46-operation REST contract covers PDF upload with multi-file merge, multi-signer signature requests with email or SMS OTP verification, pixel-placed signature zones, reusable templates, bulk campaigns, shareable public self-signing forms, pay-at-signature collection through Stripe Connect, HMAC-signed webhooks across twelve events, and download of both the signed PDF and its SHA-256 chained audit proof. Signature level is Simple Electronic Signature (SES) under eIDAS Regulation (EU) 910/2014; the provider states in its own GDPR Article 28 annex that it is not a qualified trust service provider and issues neither advanced nor qualified signatures. Bearer tokens carry one of five restrictable scopes, an Idempotency-Key makes the billable write safely repeatable, and a free sandbox needs no credit card. All data stays in the European Union.

JuriSign publishes 8 API contracts indexed on the APIs.io network, including Account API, Authentication API, Bulk API, and 5 more. Tagged areas include E-Signature, eIDAS, PDF, Webhook, and OTP.

The JuriSign catalog on APIs.io includes 1 event-driven AsyncAPI specification.

JuriSign’s developer surface includes documentation, API reference, getting-started guide, support, pricing, signup flow, authentication, and 29 more developer resources.

66.1/100 strong ▬ flat Agent 35/100 agent ready Front door AI 1/6 silent Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →
AccessFreemiumOpen⚡ Free to try
1 published contract 3 Agent Skills
E-SignatureeIDASPDFWebhookOTPGDPRFranceLegal TechIdentity VerificationAudit Traildata-residency-eu

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Developer Platform & API Ecosystem Management
BC-4270
Webhooks
GET /webhooks POST /webhooks GET /webhooks/{id}/logs
Legal Management
BC-150
Sign Requests
GET /sign-requests POST /sign-requests GET /sign-requests/{id} GET /sign-requests/{id}/download

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for JuriSign It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/jurisign/"><img src="https://apis.io/badge/jurisign/card.svg" alt="JuriSign on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/jurisign/apis.yml: open an issue on github.com/api-evangelist/jurisign to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

PDF
tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

JuriSign Account API

Credit balance and plan

JuriSign Authentication API

Obtain and revoke API tokens

JuriSign Bulk API

Merge templates and bulk campaigns (one individualised request per recipient)

JuriSign Documents API

Upload and manage PDF documents

JuriSign Public Forms API

Shareable links: each respondent signs their own generated request, no account needed

JuriSign Sign Requests API

Create, send, and track signature requests

JuriSign Templates API

Reusable sign request templates

JuriSign Webhooks API

Manage webhook endpoints for event notifications

Scroll for all 8

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Pricing Plans 1

Published pricing tiers and plan structures.

Jurisign Plans Pricing

14 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Jurisign Rate Limits

6 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Jurisign Api Overlay

10 actions · update · jurisign-api-openapi.yml

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Jurisign Authentication

http · 1 scheme

SECURITY

Jurisign Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Jurisign Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Jurisign Scopes

5 scopes

5 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
name: JuriSign
aid: jurisign
description: eIDAS electronic signature API developed in France by PCFrance and hosted in Europe. JuriSign issues Simple Electronic
  Signatures (SES) under eIDAS Regulation (EU) No 910/2014 only -- not advanced (AdES) and not qualified (QES). The 46-operation
  REST contract covers PDF upload with multi-file merge, multi-signer signature requests with email or SMS OTP verification,
  pixel-placed signature zones, reusable templates, bulk campaigns, shareable public self-signing forms, pay-at-signature
  collection through Stripe Connect, HMAC-signed webhooks across twelve events, and download of both the signed PDF and its
  SHA-256 chained audit proof. Signature level is Simple Electronic Signature (SES) under eIDAS Regulation (EU) 910/2014;
  the provider states in its own GDPR Article 28 annex that it is not a qualified trust service provider and issues neither
  advanced nor qualified signatures. Bearer tokens carry one of five restrictable scopes, an Idempotency-Key makes the billable
  write safely repeatable, and a free sandbox needs no credit card. All data stays in the European Union.
accessModel:
  pricing: freemium
  onboarding: open
  trial: false
  try_now: true
  public: true
  label: Freemium · Open access
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://www.jurisign.fr/images/icons/icon-192x192.png
url: https://raw.githubusercontent.com/api-evangelist/jurisign/refs/heads/main/apis.yml
created: '2026-08-31'
modified: '2026-08-31'
specificationVersion: '0.21'
tags:
- E-Signature
- eIDAS
- PDF
- Webhook
- OTP
- GDPR
- France
- Legal Tech
- Identity Verification
- Audit Trail
- data-residency-eu
tags_raw:
- electronic-signature
- esignature
- eidas
- document-signing
- pdf
- webhooks
- otp
- gdpr
- france
- legaltech
- identity-verification
- audit-trail
- data-residency-eu
- Electronic Signature
- Document Signing
apis:
- aid: jurisign:jurisign-account-api
  name: JuriSign Account API
  description: Credit balance and plan
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Account
  properties:
  - type: OpenAPI
    url: openapi/jurisign-account-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-authentication-api
  name: JuriSign Authentication API
  description: Obtain and revoke API tokens
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/jurisign-authentication-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-bulk-api
  name: JuriSign Bulk API
  description: Merge templates and bulk campaigns (one individualised request per recipient)
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Bulk
  properties:
  - type: OpenAPI
    url: openapi/jurisign-bulk-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-documents-api
  name: JuriSign Documents API
  description: Upload and manage PDF documents
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Documents
  properties:
  - type: OpenAPI
    url: openapi/jurisign-documents-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-public-forms-api
  name: JuriSign Public Forms API
  description: 'Shareable links: each respondent signs their own generated request, no account needed'
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Public Forms
  properties:
  - type: OpenAPI
    url: openapi/jurisign-public-forms-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-sign-requests-api
  name: JuriSign Sign Requests API
  description: Create, send, and track signature requests
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Sign Requests
  properties:
  - type: OpenAPI
    url: openapi/jurisign-sign-requests-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-templates-api
  name: JuriSign Templates API
  description: Reusable sign request templates
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Templates
  properties:
  - type: OpenAPI
    url: openapi/jurisign-templates-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
- aid: jurisign:jurisign-webhooks-api
  name: JuriSign Webhooks API
  description: Manage webhook endpoints for event notifications
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/jurisign-webhooks-api-openapi.yml
  - type: DeveloperPortal
    url: https://www.jurisign.fr/developpeurs
  - type: Documentation
    url: https://www.jurisign.fr/api/docs
  - type: APIReference
    url: https://www.jurisign.fr/api/swagger
  - type: GettingStarted
    url: https://www.jurisign.fr/api/guide
  - type: Examples
    url: examples/jurisign-examples.yml
  - type: DataModel
    url: data-model/jurisign-data-model.yml
maintainers:
- FN: JuriSign (PCFRANCE)
  email: support@jurisign.fr
  url: https://www.jurisign.fr
common:
- type: CapabilityMap
  url: capabilities/jurisign-capability-edges.yml
  name: JuriSign Business Capability Map
- type: Website
  url: https://www.jurisign.fr/
- type: DeveloperPortal
  url: https://www.jurisign.fr/developpeurs
- type: Documentation
  url: https://www.jurisign.fr/api/docs
- type: APIReference
  url: https://www.jurisign.fr/api/swagger
- type: GettingStarted
  url: https://www.jurisign.fr/api/guide
- type: Support
  url: https://www.jurisign.fr/contact
- type: HelpCenter
  url: https://www.jurisign.fr/aide
- type: Pricing
  url: https://www.jurisign.fr/tarifs
- type: SignUp
  url: https://www.jurisign.fr/register
- type: Login
  url: https://www.jurisign.fr/login
- type: TermsOfService
  url: https://www.jurisign.fr/cgu
- type: PrivacyPolicy
  url: https://www.jurisign.fr/confidentialite
- type: Authentication
  url: authentication/jurisign-authentication.yml
- type: OAuthScopes
  url: scopes/jurisign-scopes.yml
- type: Conventions
  url: conventions/jurisign-conventions.yml
- type: Idempotency
  url: conventions/jurisign-conventions.yml
- type: ErrorCatalog
  url: errors/jurisign-problem-types.yml
- type: RateLimits
  url: rate-limits/jurisign-rate-limits.yml
- type: Plans
  url: plans/jurisign-plans-pricing.yml
- type: Sandbox
  url: sandbox/jurisign-sandbox.yml
- type: Webhooks
  url: asyncapi/jurisign-webhooks.yml
- type: Lifecycle
  url: lifecycle/jurisign-lifecycle.yml
- type: Conformance
  url: conformance/jurisign-conformance.yml
- type: Compliance
  url: conformance/jurisign-conformance.yml
- type: DataModel
  url: data-model/jurisign-data-model.yml
- type: Examples
  url: examples/jurisign-examples.yml
- type: Overlay
  url: overlays/jurisign-api-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/jurisign-llms.txt
- type: Packages
  url: packages/jurisign-packages.yml
- type: WellKnown
  url: well-known/jurisign-well-known.yml
- type: SecurityTxt
  url: well-known/jurisign-security.txt
- type: Security
  url: security/jurisign-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
  url: security/jurisign-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/jurisign-domain-security.yml
x-enrichment:
  date: '2026-08-31'
  status: enriched
  artifacts_added: 26
  pass: local-v1

JuriSign API — frequently asked questions

Does JuriSign have an API?

Yes. APIs.io lists 8 APIs from JuriSign, including JuriSign Account API, JuriSign Authentication API and JuriSign Bulk API, and 5 more.

Is there an OpenAPI specification for the JuriSign API?

Yes. APIs.io indexes 8 OpenAPI specifications for JuriSign, each linked for download from this page.

How do I authenticate with the JuriSign API?

JuriSign uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Jurisign Authentication.

How much does the JuriSign API cost?

APIs.io lists 14 pricing plans for JuriSign, with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the JuriSign API ready for AI agents?

JuriSign has a Kin Score of 66.1 out of 100 (strong) and an Agent Readiness score of 34.9 (agent-ready), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/jurisign"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/jurisign/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/jurisign/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.