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

Scrive Signing API

The Signing API from Scrive — 7 operation(s) for signing.

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

Tagged areas include Signing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths. It is described by OpenAPI 3.0.3, at version 2.0.0.

Requests are made against 2 base URLs: https://scrive.com/api/v2, https://api-testbed.scrive.com/api/v2.

7 operations 7 paths 0 schemas 2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0.0
Base URL
https://scrive.com/api/v2
Authentication
OAuth 2.0, API Key
Resource Areas
1

Authentication & Security 2

Scrive Signing API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 6 scopes. An API key is passed in the header as Authorization (oauth1). By default, every request must be authenticated.

  • oauth1 — OAuth 1.0 or personal access credentials passed in the Authorization header using PLAINTEXT signatures (oauthconsumerkey, oauthtoken, oauthsignature).

Paths & Operations 7

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

Signing 7
POST
/documents/{document_id}/remind
Remind signatories
remind 1 param → 200
POST
/documents/{document_id}/forward
Forward a document
forward 1 param → 200
POST
/documents/{document_id}/restart
Restart a document
restart 1 param → 201
POST
/documents/{document_id}/{signatory_id}/resend
Resend an invitation to a signatory
resend 2 params → 200
GET
/documents/{document_id}/{signatory_id}/getqrcode
Get a sign-link QR code for a signatory
getQrCode 2 params → 200
GET
/documents/{document_id}/{signatory_id}/signingdata
Get signing data for a signatory
signingData 2 params → 200
POST
/documents/{document_id}/{signatory_id}/changemobile
Change a signatory's contact info
changeMobile 2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scrive-signing-api-openapi.yml Raw ↑

Other APIs Scrive publishes across the network.

Scrive Access Control API
Scrive Attachments API
Scrive Callbacks API
Scrive Documents API
Scrive e-ID Authentication API
Scrive Monitor API
Scrive Templates API
Where this information came from

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