Reflys Zapier API
Public API documentation for the Reflys Zapier integration.
Base URL: https://operator.reflys.com
API prefix: /api/zapier
Content-Type: application/json
Rate limit: 120 requests per minute per API key
Authentication
All Zapier API requests require a Bearer API key.
- In Reflys, go to Settings → Integrations → Zapier.
- Click Connect (or regenerate) to create an API key.
- Copy the key once (it is only shown at creation).
- In Zapier, paste the key when connecting the Reflys app (API host is fixed to production:
https://operator.reflys.com). - Keep Enable Sync turned On for outbound triggers (webhooks to Zapier).
Authorization: Bearer <REFLYS_ZAPIER_API_KEY>
Accept: application/json
The key is a Laravel Sanctum personal access token scoped to the brand with the zapier ability. Invalid or missing credentials return 401 Unauthorized.
Auth test
GET /api/zapier/me
Response 200
{
"id": 1618,
"name": "Acme Brand",
"email": "owner@example.com"
}
REST Hooks (triggers)
When a Zap that uses a Reflys trigger is turned On, Zapier subscribes to a webhook. Reflys POSTs JSON payloads to Zapier’s hookUrl when the event occurs.
Subscribe
POST /api/zapier/hooks
Body
| Field | Type | Required | Description |
|---|---|---|---|
event | string | yes | One of contact.created, contact.tag_added, form.submitted |
hookUrl | string (URL) | yes | Zapier callback URL |
tag_id | integer | no | Only for contact.tag_added — limit to one tag |
form_id | integer | no | Only for form.submitted — limit to one form |
Response 201
{ "id": 42 }
Unsubscribe
DELETE /api/zapier/hooks/{id}
Response 200
{ "ok": true }
Events and payloads
contact.created — New Contact
Fired when a contact (profile) is created in Reflys.
{
"id": 1,
"name": "Jane Doe",
"email": "jane@example.com",
"phone": "+15551234567",
"username": "jane",
"type": "zapier",
"created_at": "2026-01-01T00:00:00+00:00",
"updated_at": "2026-01-01T00:00:00+00:00"
}
contact.tag_added — Tag Added to Contact
Fired when a tag is assigned to a contact. Optional tag_id filter on subscribe.
{
"id": "tag_1_9_1700000000",
"profile_id": 1,
"tag_id": 9,
"tag_name": "VIP",
"contact": {
"id": 1,
"name": "Jane Doe",
"email": "jane@example.com",
"phone": "+15551234567",
"username": "jane",
"type": "zapier",
"created_at": "2026-01-01T00:00:00+00:00",
"updated_at": "2026-01-01T00:00:00+00:00"
},
"assigned_at": "2026-01-01T00:00:00+00:00"
}
form.submitted — New Form Submission
Fired when a Reflys form is submitted. Optional form_id filter on subscribe.
{
"id": 100,
"form_id": 5,
"form_name": "Lead Form",
"profile_id": 1,
"status": "accepted",
"payload": { "email": "jane@example.com", "name": "Jane" },
"contact": {
"id": 1,
"name": "Jane Doe",
"email": "jane@example.com",
"phone": null,
"username": null,
"type": "form",
"created_at": "2026-01-01T00:00:00+00:00",
"updated_at": "2026-01-01T00:00:00+00:00"
},
"submitted_at": "2026-01-01T00:00:00+00:00"
}
Sample data (Zapier performList)
Used when building/testing Zaps before live traffic.
| Method | Path | Description |
|---|---|---|
GET | /api/zapier/samples/contacts | Up to 3 recent contacts (or a static sample) |
GET | /api/zapier/samples/tag-added | Sample tag-added payload (tag_id query optional) |
GET | /api/zapier/samples/form-submissions | Sample form submission (form_id query optional) |
Resources (dynamic dropdowns)
List tags
GET /api/zapier/tags
[{ "id": 9, "name": "VIP" }]
List forms
GET /api/zapier/forms
[{ "id": 5, "name": "Lead Form" }]
Actions
Create / update contact
POST /api/zapier/contacts
Body
| Field | Type | Required | Description |
|---|---|---|---|
email | string | one of email/phone | Contact email |
phone | string | one of email/phone | Contact phone |
name | string | no | Display name |
username | string | no | Username |
tag_id | integer | no | Tag to assign after save |
Matches existing contacts by email (case-insensitive) or phone, then updates; otherwise creates a new contact (type: zapier).
Response 201 (created) or 200 (updated)
{
"created": true,
"contact": {
"id": 1,
"name": "Jane Doe",
"email": "jane@example.com",
"phone": null,
"username": null,
"type": "zapier",
"created_at": "2026-01-01T00:00:00+00:00",
"updated_at": "2026-01-01T00:00:00+00:00"
}
}
Add tag to contact
POST /api/zapier/contacts/tags
Body
| Field | Type | Required | Description |
|---|---|---|---|
tag_id | integer | yes | Tag ID |
profile_id | integer | one of profile_id/email | Contact ID |
email | string | one of profile_id/email | Contact email |
Response 200 — tag-added payload (same shape as the trigger).
Find contact
GET /api/zapier/contacts/search?profile_id=1
GET /api/zapier/contacts/search?email=jane@example.com
GET /api/zapier/contacts/search?phone=%2B15551234567
Provide one of profile_id, email, or phone (empty strings are ignored). Prefer profile_id when chaining from a Reflys trigger — Instagram contacts often have no email/phone. Returns a JSON array (Zapier search format): one contact, or [] if not found.
[
{
"id": 1,
"name": "Jane Doe",
"email": "jane@example.com",
"phone": "+15551234567",
"username": null,
"type": "zapier",
"created_at": "2026-01-01T00:00:00+00:00",
"updated_at": "2026-01-01T00:00:00+00:00"
}
]
Dashboard endpoints (API key management)
These are used by the Reflys web app (session/Sanctum user auth), not by Zapier runtime requests:
| Method | Path | Description |
|---|---|---|
POST | /api/integration/zapier/connect | Create/regenerate Zapier API key |
GET | /api/integration/zapier/status | Connection status, key hint, hook count |
| Disconnect | via existing integration disconnect for type=zapier | Revokes key and hook subscriptions |
Errors
| Status | Meaning |
|---|---|
401 | Missing/invalid API key |
403 | Token missing zapier ability, or brand without paid membership |
404 | Resource not found (e.g. contact for add-tag) |
422 | Validation error (JSON field → messages) |
429 | Rate limited |
Support
- Product: https://reflys.com
- API host:
https://operator.reflys.com - For Zapier connection help: Reflys → Settings → Integrations → Zapier