Sign in

v1

latestOpenAPI 3.0.32026-08-0631313.6 KB
Zapier Webhooks

Receive Zapier webhook

Receives webhook calls from Zapier for:

  • Create Client
  • Create Prospect
  • Other events (activity.logged, workout.completed, etc.)

{endpoint} is a user-specific identifier provided during connection setup.

The general envelope structure is:

{
  "id": "evt_123456",
  "event": "client.created",
  "version": "v1",
  "created": "1762263854",
  "source": "zapier",
  "endpoint_id": "wh_3fa85f64",
  "is_testing": false,
  "data": { ... }
}
post/api/integrations/webhooks/zapier/{endpoint}

Path parameters

endpointstring required

User-specific webhook endpoint identifier.

Request body

idstring required

Unique event ID.

event'activity.logged' | 'checkin.submitted' | 'client.activated' | 'client.created' | 'client.deleted' | 'prospect.created' | 'workout.completed' required

Event type identifier.

versionstring required
createdstring required

Creation timestamp (e.g. epoch seconds as string).

sourcestring required
endpoint_idstring required
is_testingboolean

Example request

{
  "id": "evt_123456",
  "version": "v1",
  "created": "1762263854",
  "source": "zapier",
  "endpoint_id": "wh_3fa85f64",
  "data": {
    "activity": "Treadmill",
    "duration": 1800,
    "distance": 1200,
    "hr": 140,
    "calories": 250
  }
}

Response

Webhook accepted

statusstring
messagestring

Example response

{
  "status": "success",
  "message": "Webhook processed."
}