Create a lead
Creates a request (e.g. from a form or Zapier). With platform_link, the request gets the identity every Joinways ingestion path writes: when a lead already carries the same request (same link, a known alias of it, or the same inquiry at the same venue), that lead is returned with existing: true and 200 instead of a duplicate. The same inquiry at another venue is a sibling request: it is created (201). source defaults to platform when given, else api. Role permission: leads.manage.
Request
- Base URL: https://joinways.app/api/v1
- URL: https://joinways.app/api/v1/leads
- Auth: one of:
- HTTP bearer
- OAuth 2 (authorization code, authorization URL https://joinways.app/oauth/authorize, token URL https://joinways.app/api/oauth/token, scopes: mcp.write)
Headers
Optional client-generated key (1 to 255 characters, e.g. a UUID v4) that makes the request idempotent for 24 hours: a retry with the same key replays the recorded response (marked Idempotency-Replayed: true) instead of executing the operation again. Same key with another body: 422 idempotency_key_reuse; while the first request runs: 409 idempotency_conflict. See the Idempotency section.
Request body
Response
The request was already in Joinways; the existing lead is returned.
Example response
{
"status": "pending",
"client_name": "Jane Doe",
"company": "Acme",
"event_type": "seminar",
"start_time": "19:00",
"inquiry_key": "kactus:184522",
"rejection_reason": "date_unavailable"
}Changes
No recorded changes to this operation across all 1 revision of this API.