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

The Documents API from Scrive — 13 operation(s) for documents.

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

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

This API exposes 13 operations across 13 paths, and defines 2 schemas. 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.

13 operations 13 paths 2 schemas 4 GET9 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 Documents 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 13

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

Documents 13
POST
/documents/new
Create a new document
newDocument body → 201
POST
/documents/{document_id}/update
Update a document
updateDocument 1 param body → 200
POST
/documents/{document_id}/setfile
Set the main file of a document
setFile 1 param body → 200
POST
/documents/{document_id}/appendfile
Append a PDF to a document
appendFile 1 param → 200
POST
/documents/{document_id}/start
Start the signing process
startDocument 1 param → 200
GET
/documents/{document_id}/get
Retrieve a document
getDocument 1 param → 200
GET
/documents/{short_document_id}/getbyshortid
Retrieve a document by short ID
getByShortId 1 param → 200
GET
/documents/list
List documents
listDocuments 4 params → 200
GET
/documents/{document_id}/canbestarted
Validate a document is ready to start
canBeStarted 1 param → 200
POST
/documents/{document_id}/prolong
Extend document expiry
prolong 1 param → 200
POST
/documents/{document_id}/cancel
Cancel a pending document
cancel 1 param → 200
POST
/documents/{document_id}/trash
Move a document to trash
trash 1 param → 200
POST
/documents/{document_id}/delete
Delete a document
deleteDocument 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Document (8 properties), Signatory (6 properties). Each schema is shown below with its type and property counts.

Signatory
object
6 properties
Document
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scrive-documents-api-openapi.yml Raw ↑

Other APIs Scrive publishes across the network.

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

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