Emergency claims routed to vetted tradespeople in seconds, not hours.
See how the API works →A policyholder calls your claims line with a burst pipe. Your handler opens a spreadsheet, rings three contractors, leaves two voicemails, and promises a callback within two hours. The claimant is watching water damage spread across their kitchen floor. Slow dispatch inflates claim costs, destroys NPS scores, and exposes you to complaints. Your panel contractors aren't the problem — the dispatch process is.
A message, sent and delivered live on the platform. TPS-screened before every send. ICO registered: ZC164080.
A claim is opened; you POST the policyholder's number and the property postcode. Only those two fields are required — who to reach and where the job is. Everything else is optional attribution.
curl -X POST https://app.pipeiq.co.uk/api/leads/register \ -H "Content-Type: application/json" \ -H "X-PipeIQ-Token: YOUR_API_KEY" \ -d '{ "mobile_number": "07700900000", "postcode": "LS1 4DY", "selected_trade": "plumbing", "utm_source": "claims-portal", "utm_campaign": "escape-of-water" }'
A 201 Created response means the lead was registered and the welcome SMS was
dispatched; the body returns the matched postcode sector. mobile_number accepts
07xxxxxxxxx or 447xxxxxxxxx. selected_trade takes plumbing,
gas, electrical, roofing, building or
all; it is not validated, so an unrecognised or omitted value is recorded as
Other rather than rejected. Full field and response reference on the
Partner API page.
Lead distribution fails quietly when nobody handles the unhappy path. One of these you must never retry.
| Code | Meaning | What to do |
|---|---|---|
201 | Lead registered, welcome SMS dispatched | Store the returned postcode sector against the lead. |
400 | Missing or invalid fields | Fix the payload; do not retry unchanged. |
401 | Invalid or missing API key | Check the header. Never put the key in client-side code. |
405 | Wrong HTTP method | POST only. OPTIONS returns 200 for CORS preflight; everything else is rejected. |
422 | Number previously opted out | Do not retry. Mark the lead unreachable by SMS and route it another way. |
429 | Daily call limit reached (100 per key per 24h) | Back off and resume; email support to raise the cap. Sandbox keys share this status. |
500 | Unexpected server error | Retry with backoff; contact support with your request id if it persists. |
The 422 is the one worth designing around. It is not a transport failure, it is a lawful-basis answer: that person has told us not to text them. Retrying it is the easiest way to turn a compliance feature into a compliance incident.