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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Unified.to

Unified.to signing API

The signing API from Unified.to — 6 operation(s) for signing.

Documentation Provider Profile APIs.io OpenAPI GitHub

Unified.to signing API is one of 140 APIs that Unified.to publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 13 JSON Schema definitions.

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

This API exposes 14 operations across 6 paths, and defines 6 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against 3 base URLs: https://api.unified.to, https://api-eu.unified.to, https://api-au.unified.to.

14 operations 6 paths 6 schemas 2 DELETE6 GET2 PATCH2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Servers
https://api.unified.to
https://api-eu.unified.to
https://api-au.unified.to
Authentication
API Key
Contact
https://unified.to/contact
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Unified.to signing API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (jwt). By default, every request must be authenticated.

Paths & Operations 14

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

signing 14
GET
/signing/{connection_id}/document
List All Documents
listSigningDocuments 11 params → 200
POST
/signing/{connection_id}/document
Create a Document
createSigningDocument 3 params body → 200
DELETE
/signing/{connection_id}/document/{id}
Remove a Document
removeSigningDocument 2 params → 200default
GET
/signing/{connection_id}/document/{id}
Retrieve a Document
getSigningDocument 4 params → 200
PATCH
/signing/{connection_id}/document/{id}
Update a Document
patchSigningDocument 4 params body → 200
PUT
/signing/{connection_id}/document/{id}
Update a Document
updateSigningDocument 4 params body → 200
GET
/signing/{connection_id}/signatory
List All Signatories
listSigningSignatories 10 params → 200
POST
/signing/{connection_id}/signatory
Create a Signatory
createSigningSignatory 3 params body → 200
DELETE
/signing/{connection_id}/signatory/{id}
Remove a Signatory
removeSigningSignatory 2 params → 200default
GET
/signing/{connection_id}/signatory/{id}
Retrieve a Signatory
getSigningSignatory 4 params → 200
PATCH
/signing/{connection_id}/signatory/{id}
Update a Signatory
patchSigningSignatory 4 params body → 200
PUT
/signing/{connection_id}/signatory/{id}
Update a Signatory
updateSigningSignatory 4 params body → 200
GET
/signing/{connection_id}/template
List All Templates
listSigningTemplates 9 params → 200
GET
/signing/{connection_id}/template/{id}
Retrieve a Template
getSigningTemplate 4 params → 200

Schemas 6

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

SigningDocument
object
13 properties
SigningTemplate
object
8 properties
SigningDocuments
array
SigningTemplates
array
SigningSignatories
array
SigningSignatory
object
12 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unified-to-signing-api-openapi.yml Raw ↑

Other APIs Unified.to publishes across the network.

Unified.to
AE Profile APIs.io
Unified.to Authentication API
AE Profile APIs.io
Unified.to account API
AE Profile APIs.io
Unified.to accounting API
AE Profile APIs.io
Unified.to activity API
AE Profile APIs.io
Unified.to ad API
AE Profile APIs.io
Unified.to ads API
AE Profile APIs.io
Unified.to apicall API
AE Profile APIs.io
Unified.to application API
AE Profile APIs.io
Unified.to applicationstatus API
AE Profile APIs.io
Unified.to assessment API
AE Profile APIs.io
Unified.to ats API
AE Profile APIs.io
#Signing
← Back to U APIs
API Details
ID
unified-to:unified-to-signing-api
Server
https://api.unified.to
Docs
https://unified.to/
Provider
Unified.to
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=unified-to-signing-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/unified-to-signing-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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