How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

JuriSign Sign Requests API

Create, send, and track signature requests

JuriSign Sign Requests API is one of 8 APIs that JuriSign publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sign Requests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 7 operations across 6 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 3.24.1.

Requests are made against a single base URL, https://jurisign.fr/api/v1.

7 operations 6 paths 5 schemas 4 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.24.1
Base URL
https://www.jurisign.fr/api/v1
Authentication
HTTP Bearer
License
Proprietary
Resource Areas
1

Authentication & Security 1

JuriSign Sign Requests 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 7

Across 6 paths, the API surfaces 7 operations — 4 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Sign Requests 7

Create, send, and track signature requests

GET
/sign-requests
List Sign Requests
listSignRequests 3 params → 200401
POST
/sign-requests
Create Sign Request
createSignRequest 1 param body → 201401422409
GET
/sign-requests/{id}
Get Sign Request
getSignRequest 1 param → 200401404
POST
/sign-requests/{id}/send
Send Sign Request
sendSignRequest 1 param → 200401404422
POST
/sign-requests/{id}/cancel
Cancel Sign Request
cancelSignRequest 1 param → 200401404422
GET
/sign-requests/{id}/download
Download Signed PDF
downloadSignedPdf 1 param → 200401404
GET
/sign-requests/{id}/proof
Download Audit Proof
downloadProof 1 param → 200401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are SignRequest (16 properties), CreateSignRequestInput (11 properties), SignatureZone (9 properties), Pagination (4 properties). Each schema is shown below with its type and property counts.

Pagination
object
4 properties
CreateSignRequestInput
object
11 properties 5 required
SignatureZone
object
9 properties
SignRequest
object
16 properties
SignRequestDetailed

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jurisign-sign-requests-api-openapi.yml Raw ↑

Other APIs JuriSign publishes across the network.

JuriSign Account API
JuriSign Authentication API
JuriSign Bulk API
JuriSign Documents API
JuriSign Public Forms API
JuriSign Templates API
JuriSign Webhooks API
Where this information came from

This is an independent, third-party profile of JuriSign Sign Requests 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.