API and webhooks

Last updated: November 6, 2026

Connect URETC to Zapier, Make, n8n, Pabbly Connect, Pipedream or your own code. API access is included on the Pro and Enterprise plans. Create a key in the app under Integrations. Keys act as the agent who created them and are limited to the permissions you choose. The machine-readable description is at /api/v1/openapi.json (OpenAPI 3.1).

Authentication and limits

  • Send Authorization: Bearer uretc_live_… with every request to https://uretc.com/api/v1.
  • 120 requests a minute per key. Responses include X-RateLimit-Limit and X-RateLimit-Remaining; a 429 includes Retry-After.
  • Errors look like {"error":{"code":"…","message":"…"}}. Lists are paged with limit and cursor (use next_cursor).
  • Keys are shown once and stored only as a hash. Revoke a key any time; its webhooks stop with it.

Permissions (scopes)

  • transactions:read: Read transactions, dates and status
  • transactions:write: Change status and key dates
  • clients:read: Read clients
  • clients:write: Add clients
  • tasks:read: Read tasks
  • tasks:write: Create and complete tasks
  • documents:read: List documents and get short-lived download links
  • webhooks:manage: Subscribe to events (Zapier, Make, n8n)

Endpoints

  • GET /me: The agent this key acts as, and its scopes
  • GET /transactions: List transactions (newest first) (transactions:read)
  • GET /transactions/{id}: Get a transaction (transactions:read)
  • PATCH /transactions/{id}: Change stage or key dates (closing out happens in the app) (transactions:write)
  • GET /transactions/{id}/tasks: List tasks on a transaction (tasks:read)
  • POST /transactions/{id}/tasks: Add a task (tasks:write)
  • GET /transactions/{id}/documents: List documents (optionally with 5-minute download links; every link is logged) (documents:read)
  • PATCH /tasks/{id}: Update a task status (tasks:write)
  • GET /clients: List your clients (clients:read)
  • POST /clients: Add a client (no email is sent) (clients:write)
  • GET /clients/{id}: Get a client (clients:read)
  • GET /webhooks: Webhooks created with this key (webhooks:manage)
  • POST /webhooks: Subscribe a URL to events (Zapier / Make / n8n REST hooks) (webhooks:manage)
  • DELETE /webhooks/{id}: Unsubscribe (webhooks:manage)

Webhooks

Subscribe a URL to events from the app (Integrations, then Webhooks) or with POST /webhooks, which is how Zapier-style “instant” triggers subscribe and unsubscribe. We POST JSON like {"id":"evt_…","type":"transaction.closed","created_at":"…","data":{…}}. Failed deliveries are retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours; an endpoint that fails 25 times in a row is switched off. Responding 410 Gone unsubscribes it.

  • transaction.created: A transaction was created
  • transaction.status_changed: A transaction moved to a new stage
  • transaction.closed: A transaction closed (completed)
  • transaction.fell_through: A transaction was cancelled or fell through
  • task.completed: A task was completed
  • document.uploaded: A document was uploaded
  • client.created: A client was added
  • email.ready: A client email was prepared: sent from your mailbox, waiting as a draft, or handed off for your own email tool (see status)

Each delivery is signed. Check the signature before trusting it:

// Node.js: verify a webhook delivery
const crypto = require('crypto')
function verify(rawBody, header, secret) {
  const parts = Object.fromEntries(header.split(',').map((p) => p.split('=')))
  const expected = crypto.createHmac('sha256', secret).update(parts.t + '.' + rawBody).digest('hex')
  const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300
  return fresh && crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1))
}

Connecting Zapier, Make or n8n today

  1. Create a key with the permissions your workflow needs.
  2. For a trigger, use the tool's “webhook” or “catch hook” step, copy its URL and add it under Webhooks with the events you want (for example transaction.closed to add a past client to a Mailchimp audience).
  3. For an action, use the tool's HTTP request step with your key in the Authorization header.

Questions? Contact support. Using the API means you agree to our Terms; keep keys secret and don't use the API to send unsolicited messages.