SignWell
E-signature platform with a REST API for sending documents for signature, creating templates, tracking document status, and managing signers programmatically. Supports embedded signing, bulk send, webhooks, and white-label customization with compliance for ESIGN, UETA, GDPR, and HIPAA.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles SignWell the way a machine reads it — 128 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SignWell scores 59.9/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile SignWell
Each block below is one kind of artifact we hold for SignWell. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SignWell API Application API
Manage API application settings and branding.
SignWell Bulk Send API
Send a document to multiple recipients in batch using templates.
SignWell Document API
Create, send, and manage documents for electronic signing.
SignWell Me API
Retrieve account information for the authenticated API key.
SignWell Regional API
Access region-specific endpoints for data residency compliance.
SignWell Template API
Create and manage reusable document templates.
SignWell Webhooks API
Subscribe to document lifecycle events via webhook callbacks.
Scroll within the panel for all 7 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
SignWell GraphQL Schema
This document describes the conceptual GraphQL schema for the SignWell e-signature API. SignWell provides a REST API at https://www.signwell.com/api/v1 for sending documents for...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Signwell Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Signwell Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Signwell Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
SignWell API Rules
SPECTRALJSON Schema 84
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccountInfoResponse
JSON SCHEMAAdditionalFields
JSON SCHEMAAdditionalFiles
JSON SCHEMAApiApplicationId
JSON SCHEMAApiApplicationResponse
JSON SCHEMAAttachmentRequestInfo
JSON SCHEMAAttachmentRequests
JSON SCHEMABase64Flag
JSON SCHEMABulkSendCreateResponse
JSON SCHEMABulkSendCsv
JSON SCHEMABulkSendCsvRequest
JSON SCHEMABulkSendCsvTemplateResponse
JSON SCHEMABulkSendDocumentsResponse
JSON SCHEMABulkSendId
JSON SCHEMABulkSendListItem
JSON SCHEMABulkSendListResponse
JSON SCHEMABulkSendResponse
JSON SCHEMABulkSendTemplateIds
JSON SCHEMABulkSendValidateCsvResponse
JSON SCHEMACheckboxGroupInfo
JSON SCHEMACheckboxGroups
JSON SCHEMACheckboxValidation
JSON SCHEMACompletedDocumentId
JSON SCHEMACompletedPdfBinaryResponse
JSON SCHEMACompletedPdfResponse
JSON SCHEMACompletedPdfUrlResponse
JSON SCHEMACompletedPdfZipResponse
JSON SCHEMACopiedContactInfo
JSON SCHEMACopiedContacts
JSON SCHEMACopiedPlaceholders
JSON SCHEMACreateBulkSendRequest
JSON SCHEMADateFormat
JSON SCHEMADocumentFromTemplateRequest
JSON SCHEMADocumentFromTemplateResponse
JSON SCHEMADocumentId
JSON SCHEMADocumentListResponse
JSON SCHEMADocumentRequest
JSON SCHEMADocumentResponse
JSON SCHEMADocumentTemplateListResponse
JSON SCHEMADocumentTemplateRequest
JSON SCHEMADocumentTemplateResponse
JSON SCHEMADocumentTemplateUpdateRequest
JSON SCHEMADropdownOption
JSON SCHEMAErrorResponse
JSON SCHEMAFieldType
JSON SCHEMAFields
JSON SCHEMAFileFormat
JSON SCHEMAFileInfo
JSON SCHEMAFiles
JSON SCHEMAIncludeAuditPage
JSON SCHEMALabelInfo
JSON SCHEMALabelRequest
JSON SCHEMALabelResponse
JSON SCHEMALabels
JSON SCHEMALabelsResponse
JSON SCHEMALabelsUpdate
JSON SCHEMALimit
JSON SCHEMAMeResponse
JSON SCHEMANom151CertificateResponse
JSON SCHEMANom151UrlResponse
JSON SCHEMAObjectOnly
JSON SCHEMAPage
JSON SCHEMAPaginationMeta
JSON SCHEMAPlaceholders
JSON SCHEMARateLimitErrorResponse
JSON SCHEMARecipients
JSON SCHEMAReminderRecipients
JSON SCHEMASendReminderRequest
JSON SCHEMATemplateAttachmentRequests
JSON SCHEMATemplateCheckboxGroups
JSON SCHEMATemplateFieldValues
JSON SCHEMATemplateFields
JSON SCHEMATemplateId
JSON SCHEMATemplateIds
JSON SCHEMATemplateRecipients
JSON SCHEMATextValidation
JSON SCHEMAUpdateDocumentAndSendRequest
JSON SCHEMAUrlOnly
JSON SCHEMAUserEmail
JSON SCHEMAValidationErrorResponse
JSON SCHEMAWebhookListResponse
JSON SCHEMAWebhookResponse
JSON SCHEMAupdate_recipients_map
JSON SCHEMAupdate_recipients_request
JSON SCHEMAScroll within the panel for all 84 ·
Examples 27
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Createbulksend
EXAMPLECreatedocument
EXAMPLECreatedocumentfromtemplate
EXAMPLECreatetemplate
EXAMPLECreatewebhook
EXAMPLEDeleteapiapplication
EXAMPLEDeletedocument
EXAMPLEDeletetemplate
EXAMPLEDeletewebhook
EXAMPLEGetapiapplication
EXAMPLEGetbulksend
EXAMPLEGetbulksendcsvtemplate
EXAMPLEGetbulksenddocuments
EXAMPLEGetcompletedpdf
EXAMPLEGetdocument
EXAMPLEGetme
EXAMPLEGetnom151Certificate
EXAMPLEGettemplate
EXAMPLEListbulksends
EXAMPLEListdocuments
EXAMPLEListtemplates
EXAMPLEListwebhooks
EXAMPLESenddocument
EXAMPLESendreminder
EXAMPLEUpdaterecipients
EXAMPLEUpdatetemplate
EXAMPLEValidatebulksendcsv
EXAMPLEScroll within the panel for all 27 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for SignWell — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/signwell · machine-readable index on apis.io