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 Webhooks API

Manage webhook endpoints for event notifications

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

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

This API exposes 6 operations across 4 paths, and defines 4 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.

6 operations 4 paths 4 schemas 1 DELETE2 GET2 POST1 PUT

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 Webhooks 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 6

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

Webhooks 6

Manage webhook endpoints for event notifications

GET
/webhooks
List Webhook Endpoints
listWebhooks → 200401
POST
/webhooks
Create Webhook Endpoint
createWebhook body → 201401422
PUT
/webhooks/{id}
Update Webhook Endpoint
updateWebhook 1 param body → 200401403404
DELETE
/webhooks/{id}
Delete Webhook Endpoint
deleteWebhook 1 param → 200401403404
GET
/webhooks/{id}/logs
Webhook Delivery Logs
getWebhookLogs 2 params → 200401403
POST
/webhooks/{id}/regenerate-secret
Regenerate Webhook Secret
regenerateWebhookSecret 1 param → 200401403

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are WebhookEndpoint (7 properties), WebhookLog (7 properties), Pagination (4 properties), MessageResponse (1 property). Each schema is shown below with its type and property counts.

MessageResponse
object
1 property
Pagination
object
4 properties
WebhookLog
object
7 properties
WebhookEndpoint
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jurisign-webhooks-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 Sign Requests API
JuriSign Templates API
Where this information came from

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