JuriSign

eIDAS-compliant electronic signature API built, operated and hosted in France by PCFRANCE. 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 1 API on the APIs.io network: REST API. Tagged areas include Electronic Signature, E-Signature, eIDAS, Document Signing, and PDF.

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 27 more developer resources.

62.7/100 strong ▬ flat Agent 41/100 agent native Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2
1 APIs
Electronic SignatureE-SignatureeIDASDocument SigningPDFWebhookOTPGDPRFranceLegal TechIdentity VerificationAudit Traildata-residency-eu

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2
Composite quality — 62.7/100 · strong
Contract Quality 16.5 / 25
Developer Ergonomics 13.8 / 20
Access Clarity 16.8 / 20
Operational Transparency 6.5 / 13
Contract Governance 2.2 / 12
Discoverability 6.9 / 10
Agent readiness — 41/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/jurisign: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

JuriSign REST 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 form...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Jurisign Rate Limits

6 limits

RATE LIMITS

Event Specifications 1

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

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

OAuth 2.0 · no documented scopes

0 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

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
name: JuriSign
aid: jurisign
description: eIDAS-compliant electronic signature API built, operated and hosted in France by PCFRANCE. 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.
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:
- Electronic Signature
- E-Signature
- eIDAS
- Document Signing
- 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
apis:
- name: JuriSign REST API
  description: '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.'
  humanURL: https://www.jurisign.fr/developpeurs
  baseURL: https://www.jurisign.fr/api/v1
  tags:
  - Electronic Signature
  - E-Signature
  - eIDAS
  - Document Signing
  - PDF
  - Webhook
  - OTP
  - GDPR
  - France
  - Legal Tech
  tags_raw:
  - electronic-signature
  - esignature
  - eidas
  - document-signing
  - pdf
  - webhooks
  - otp
  - gdpr
  - france
  - legaltech
  properties:
  - type: OpenAPI
    url: openapi/jurisign-api-openapi.yml
  - type: OpenAPI
    url: https://www.jurisign.fr/api/openapi.json
  - 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: Overlay
    url: overlays/jurisign-api-overlay.yaml
  - 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: 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

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 email required.

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