Your agreements, in your own code.

curl https://termn.ai/api/v1/me \
  -H "Authorization: Bearer $TERMN_TOKEN"

The reply names the organization the token belongs to and the scope it carries. Every other call is scoped to that organization: another organization’s record reads as not found, never as forbidden, so a wrong token never confirms that a record exists.

Sync a CRM record into a draft, then hand the send to a person

BASE=https://termn.ai/api/v1
AUTH="Authorization: Bearer $TERMN_TOKEN"
JSON="Content-Type: application/json"

# 1. The customer, keyed by your CRM id — re-running this never duplicates.
CONTACT=$(curl -s "$BASE/contacts" -H "$AUTH" -H "Idempotency-Key: sync-cust-42" -H "$JSON" \
  -d '{"display_name":"Brightline Inc","kind":"corporation",
       "email":"legal@brightline.example","external_reference":"crm-42"}' | jq -r .id)

# 2. A workspace for the deal, and a draft inside it.
WORKSPACE=$(curl -s "$BASE/workspaces" -H "$AUTH" -H "Idempotency-Key: ws-42" -H "$JSON" \
  -d '{"name":"Brightline onboarding"}' | jq -r .id)
AGREEMENT=$(curl -s "$BASE/agreements" -H "$AUTH" -H "Idempotency-Key: agr-42" -H "$JSON" \
  -d "{\"workspace_id\":\"$WORKSPACE\",\"name\":\"Data processing agreement\"}" | jq -r .id)

# 3. Attach a signer, then read readiness. proposal_ready:true means propose;
#    any other blocker means a person finishes setup at the draft's app_url
#    (documents and steps are configured there, not over the API).
curl -s "$BASE/agreements/$AGREEMENT/participants" -H "$AUTH" \
  -H "Idempotency-Key: part-42" -H "$JSON" \
  -d "{\"contact_id\":\"$CONTACT\",\"roles\":[\"signer\"]}" > /dev/null
curl -s "$BASE/agreements/$AGREEMENT" -H "$AUTH" \
  | jq '{proposal_ready, publish_blockers, app_url}'

# 4. Propose. Send the response's confirm_url to the person who decides, then
#    poll GET $BASE/proposals/<id> for state and the decision note.
curl -s "$BASE/proposals" -H "$AUTH" -H "Idempotency-Key: prop-42" -H "$JSON" \
  -d "{\"action\":\"publish_agreement\",\"agreement_id\":\"$AGREEMENT\",
       \"note\":\"Q3 onboarding, approved by legal\"}" | jq '{state, confirm_url}'

Run a trust’s funding from your book of record

BASE=https://termn.ai/api/v1
AUTH="Authorization: Bearer $TERMN_TOKEN"
JSON="Content-Type: application/json"

# 1. The people, keyed by your own ids — re-running any step here never duplicates.
SETTLOR=$(curl -s "$BASE/contacts" -H "$AUTH" -H "Idempotency-Key: tc-c-90" -H "$JSON" \
  -d '{"display_name":"Margaret Hartwell","email":"margaret@example.com",
       "external_reference":"tc-person-90"}' | jq -r .id)

# 2. One workspace per client or matter, then the trust — a Contact plus a
#    funding record. Your reference makes the create an upsert (200 on repeat).
WORKSPACE=$(curl -s "$BASE/workspaces" -H "$AUTH" -H "Idempotency-Key: tc-ws-90" -H "$JSON" \
  -d '{"name":"Hartwell estate plan"}' | jq -r .id)
TRUST=$(curl -s "$BASE/trusts" -H "$AUTH" -H "Idempotency-Key: tc-t-90" -H "$JSON" \
  -d "{\"workspace_id\":\"$WORKSPACE\",
       \"formal_name\":\"Hartwell Family Trust dated 3 March 2019\",
       \"settlor_contact_ids\":[\"$SETTLOR\"],\"trustee_contact_ids\":[\"$SETTLOR\"],
       \"external_reference\":\"tc-trust-881\"}" | jq -r .id)

# 3. Every asset that should move, listed cheaply — a label is enough, and a
#    row contacts nobody. Sort each one when you know more: the verb, the kind,
#    and the kind-shaped facts. `missing_facts` tells you what's still needed.
ITEM=$(curl -s "$BASE/funding-items" -H "$AUTH" -H "Idempotency-Key: tc-i-17" -H "$JSON" \
  -d "{\"workspace_id\":\"$WORKSPACE\",\"trust_id\":\"$TRUST\",
       \"label\":\"the Cypress Lane house\",\"asset_kind\":\"real_property\",
       \"external_reference\":\"tc-asset-17\"}" | jq -r .id)
curl -s -X PATCH "$BASE/funding-items/$ITEM" -H "$AUTH" -H "$JSON" \
  -d '{"verb":"retitle","detail":{"county":"Marin"}}' | jq '{phase, missing_facts}'

# 4. The schedule is the honest denominator: `summary.done` counts only
#    confirmed transfers and explicitly closed rows — a claim never moves it.
curl -s "$BASE/workspaces/$WORKSPACE/funding" -H "$AUTH" | jq .summary

# 5. Paper ready rows into a draft, then propose the send. A member confirms
#    at confirm_url; you hear the decision on the proposal.* webhooks, and
#    every later state change lands as trust.*, funding_item.*, movement.*,
#    and obligation.* events — no polling loop required.
AGREEMENT=$(curl -s "$BASE/funding-items/paper" -H "$AUTH" \
  -H "Idempotency-Key: tc-p-17" -H "$JSON" \
  -d "{\"item_ids\":[\"$ITEM\"]}" | jq -r .id)
curl -s "$BASE/proposals" -H "$AUTH" -H "Idempotency-Key: tc-pr-17" -H "$JSON" \
  -d "{\"action\":\"publish_agreement\",\"agreement_id\":\"$AGREEMENT\"}" \
  | jq '{state, confirm_url}'

Export the ledger to a warehouse

# Page through every open row; unknown filters fail with a 422 rather than
# silently widening the export. `agreement_id`, `workspace_id`, and `product`
# narrow it; `amount_minor` is the arithmetic-safe field.
curl -s "https://termn.ai/api/v1/ledger?include_done=false&limit=200&offset=0" \
  -H "Authorization: Bearer $TERMN_READONLY_TOKEN"
# Repeat, adding 200 to offset, while `pagination.has_more` is true.

React to a settled payment

# Verify the signature (above), then branch on the event type.
# movement.reconciled → the money provably arrived; fetch the movement for
# `confirmed_by`, `confirmed_at`, and `confirmation_basis`.
curl -s https://termn.ai/api/v1/movements/$MOVEMENT_ID \
  -H "Authorization: Bearer $TERMN_READONLY_TOKEN"