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

Certifaction Signing API

Sign files and request signatures

Certifaction Signing API is one of 6 APIs that Certifaction 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.

This API exposes 9 operations across 9 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, http://localhost:{port}.

9 operations 9 paths 7 schemas 2 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.certifaction.io
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Certifaction Signing API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_key). By default, every request must be authenticated.

Paths & Operations 9

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

Signing 9

Sign files and request signatures

POST
/prepare
Prepare a file for signing
prepare_file 12 params body → 200400401
POST
/sign
Sign a file
sign_file 20 params body → 200400401
POST
/request/create
Request a signature
request_signature 35 params body → 200400401409
POST
/request/cancel
Cancel signature request for signer
cancel_request 2 params body → 204400401403404
POST
/request/cancel/all
Cancel signature requests for file
cancel_request_all 1 param body → 204400401403404
POST
/request/listdeprecated
List signature requests for file
list_requests body → 200400401403404
GET
/request/status
Show status of signature request
request_status 2 params → 200400401403404
GET
/request/file/status
Show status of signature requests of given file
file_requests_status 2 params → 200400401403404
POST
/qes/check
Check account QES status
postQesCheck body → 200400401404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are user (26 properties), identity (14 properties), organization (4 properties). Each schema is shown below with its type and property counts.

legal_weight
string
language
string
identity
object
14 properties 12 required
prepare_scope
string
organization
object
4 properties 1 required
user
object
26 properties
envelope_item_status
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

certifaction-signing-api-openapi.yml Raw ↑

Other APIs Certifaction publishes across the network.

Certifaction Account API
Certifaction Documents API
Certifaction Organization API
Certifaction Server API
Certifaction Teamspace API
Where this information came from

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