esign
The esign noun — identity, lifecycle, events, and every capability as an anchored section: 1 capability, 0 live, 1 sandbox, 0 declared.
esign is one of the estate's 317 automotive nouns — a job a car needs done. It carries 1 capability: 0 live, 1 sandbox, 0 declared · doors docs.vin.
Identity
| Noun | esign |
| Pillar | Services (facets: 1 services) |
| Capabilities | 1 — 0 live · 1 sandbox · 0 declared |
| Entities | SignatureCeremony |
| Doors | docs.vin |
| SDK | Vin.esign.* from apis.vin |
| Address | /catalog/esign#{action} — the anchor IS the wire name minus esign. |
Events
The vocabulary this noun can append to the record — 2 past-tense, versioned event types, each linked to the capability that emits it:
Ceremony.opened@1— emitted byopenDocument.signed@1— emitted byopen
Apply & book
open
esign.open · POST /esigns/open · gate human · sandbox · answers SignatureCeremony@1
| Field | Type | Required | Notes |
|---|---|---|---|
subject | string | yes | — |
packetId | string | no | — |
signers | array<object> | no | — |
The gate is a 403 NEEDS_HUMAN — the human verb sign · demand side, routed to a named, staffed, priced terminus with a poll rail. Never a dead end. Price: not posted — see /pricing.
Door — docs.vin serves this noun on its two routes: / (the landing) · /1FTFW6L82RFB90620 (the VIN lens).
Try it — sandbox: every call answers a deterministic, provenance-labeled simulated payload ({ environment, simulated } in the body). Force any documented outcome with the magic triggers. Going live is a connect, never a ballot: submit the credential at integrates.vin (dealer systems) or connects.vin (consumer accounts) — submissions enter the activation queue and rank live rollout.
Emits — Ceremony.opened@1 · Document.signed@1.
import { esign } from 'apis.vin'
// the gate law is in the type system: Answer<T> = Ok | Empty | Blocked | Offer
const answer = await esign.open({"subject":"subject"})curl -X POST https://apis.vin/esigns/open \
-H 'content-type: application/json' \
-d '{"subject":"subject"}'Receipt — the sandbox wire answered the request above with this exact body at build time. Captured by the receipts runner (timestamped, provenance in the payload), never authored; it re-executes only when this descriptor changes.
{
"type": "OK",
"answers": "SignatureCeremony@1",
"value": {
"id": "esign_d82e4bf2",
"packetId": "document_e401db56",
"subjectId": "deal_fcb5dc48",
"signers": []
},
"evidence": {
"id": "esign_d82e4bf2",
"packetId": "document_e401db56",
"subjectId": "deal_fcb5dc48",
"signers": []
},
"provenance": {
"simulated": true,
"environment": "sandbox",
"source": "esign-sandbox"
},
"events": [],
"meter": {
"charged": "0.00",
"posted": false
}
}Data model
The record shape behind this noun — one entity, each property an evidence field. See the whole estate model on the data model page.
SignatureCeremony
Generated from the catalog. Every capability, answer, gate, and entity on this page is a rendered descriptor — it cannot drift from the wire.
engine
The engine noun — identity, lifecycle, events, and every capability as an anchored section: 25 capabilities, 2 live, 23 sandbox, 0 declared.
esignature
The esignature noun — identity, lifecycle, events, and every capability as an anchored section: 10 capabilities, 0 live, 10 sandbox, 0 declared.