Scheduling, jobs, follow-ups, and automation triggers

Core endpoints

• GET /v1/availability — resolve open slots for a user or team
• POST /v1/appointments — book an appointment
• GET /v1/jobs / GET /v1/jobs/{id} — read jobs
• POST /v1/follow-ups — schedule a follow-up
• POST /v1/playbooks/{id}/run — execute a Jarvis playbook

Query availability

curl "https://api.urbld.com/v1/availability?user_id=user_01H&from=2026-07-10&to=2026-07-12" \
  -H "Authorization: Bearer $TOKEN"

Book an appointment

await fetch("https://api.urbld.com/v1/appointments", {
  method: "POST",
  headers: { Authorization: `Bearer ${token}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    lead_id: leadId,
    starts_at: "2026-07-10T14:00:00-05:00",
    duration_minutes: 60,
    assigned_to: "user_01HABC",
    type: "estimate",
    location: { address: "123 Elm St, Austin, TX 78701" },
  }),
});

Automation triggers

Every workflow mutation fires a webhook event. Common triggers your systems will care about:

• lead.qualified — hand off to your dispatcher
• appointment.booked — sync to Google/Outlook calendar
• job.completed — trigger warranty enrollment or NPS survey
• invoice.paid — sync to accounting

See the full list on Webhooks.

Related

• Scheduling feature page
• Jobs feature page
• AI Follow-Up feature page