1. Webhook
Repairy Partner API
  • Welcome 👋
  • Get Started
  • HTTP Headers
  • Authorization
  • Workshops
  • Bookings
  • Quotes
  • Service Reminder
  • Data Reporting
  • Booking URL
  • Error Codes
  • Technical Support
  • Changelog
  • Additional Services
  • Service Catalog
  • APIs
    • Authorization
      • Access Token
      • Refresh Token
    • Workshops
      • Availabilities
      • Service Catalog
    • Bookings
      • Booking Request with Service Catalog (beta)
      • Booking Request
      • Booking Information
      • Update Booking Information
      • Update Booking Status
    • Quotes
      • Quote Request
    • Service Reminder
      • Service Reminder Notification
      • Service Reminder Information
    • Data Reporting
      • Partner Report
    • Leads
      • Call Lead
    • Messaging
      • Send Message
      • List of Templates
    • Campaigns
      • Trigger Automation
      • Blast List
      • Trigger Blast
      • Find Blast
    • Webhooks
      • Call History Webhook
  • Data Structures
    • AuthResponse
    • Availability
    • CustomAvailability
    • Car
    • Customer
    • Booking
    • BookingUpdateRequest
    • BookingStatusUpdateConfig
    • Quote
    • ServiceHistory
    • ServiceReminder
    • WebhookRequest
    • ServiceCatalog
    • CallLead
  • Webhook
    • Booking events
    • Call history
  • Schemas
    • Schemas
      • WebhookRequest
      • ServiceSelection
      • ServiceCatalogItem
      • CallLead
      • Booking
      • BookingUpdateRequest
      • Customer
      • Car
      • Availability
      • CustomAvailability
      • AuthResponse
      • Quote
      • ServiceHistory
      • ServiceReminder
      • BookingStatusUpdateConfig
  1. Webhook

Call history

Your phone system sends each finished call to Repairy. Calls show on the shop's Calls page under your system's name.
Dashboard setup: Settings → Integration → Webhooks → Call history.
Full request and response reference: Call History Webhook.

How it works#

1.
Turn on Call history for the shop and copy the Webhook URL and Secret.
2.
Your phone provider POSTs each finished call to that URL with the secret.
3.
Repairy saves the call in Call History (or links it to an existing Carrier/Chloe call).

Webhook URL and Secret#

The URL looks like:
POST https://<api host>/api/webhooks/calls/:shopId
Authenticate with the per-shop secret from the Call history page:
Header x-webhook-secret: <secret>, or
Authorization: Bearer <secret>
Use Show / Copy / Rotate on the Secret row in the dashboard. Rotating invalidates the previous secret.

Live / Dev mode#

Next to the on/off switch:
Live — calls are saved to Call History (and missed-call SMS may send when enabled).
Dev — requests are checked and listed under Received calls for 24 hours as what would be saved, but nothing is saved and no SMS is sent. Invalid payloads still return 400.

Setup guide and docs#

On the Call history page:
Setup guide — payload fields, call types, and sample JSON / cURL
Repairy API Documentation — this partner docs site
API reference: Call History Webhook

How duplicate calls are handled#

If the shop also has a Repairy line (Carrier) or Chloe, the same call can arrive twice. When a webhook call matches an existing Carrier/Chloe call with the same customer number and direction that started within 2 minutes, Repairy links your details onto that call instead of creating a second one. No extra SMS is sent. It is safe to send every call.
The dashboard includes How duplicate calls are handled with examples (same call counted once, caller calls back, caller dials the shop directly).

Send missed-call SMS#

Optional toggle on the Call history page: Inbound missed calls only. It also needs Missed call follow-up on in Call handling. Re-sending the same callId updates the call and does not send a second SMS.

Auto transcribe and Call scoring#

These follow the shop's existing Call recording / Call scoring settings (read-only status on the Call history page, with links to change them elsewhere).
Transcripts sent by your provider are always used.
If you send only a recordingUrl, Repairy may transcribe when Call recording is on.
There is no summary field — Repairy writes the summary, action items, and score.

What to send#

Finished calls only (ringing / in-progress → 400). Required fields: callId, direction, status, from, to, startedAt. Optional: recording, transcript, staff (answeredBy), line, provider name, and more — see Call History Webhook.
Calldirectionstatus
Inbound answeredinboundanswered
Inbound missedinboundmissed, voicemail
Outbound answeredoutboundanswered
Outbound unreachedoutboundno-answer, busy, failed, canceled

Responses#

StatusMeaning
201At least one call was created
200Updated, linked, or logged as test / Dev mode
400Validation failed
401Webhook off, or wrong secret

Related#

Outbound booking notifications: Booking events
API reference: Call History Webhook
Modified at 2026-11-09 10:12:10
Previous
Booking events
Next
WebhookRequest
Built with