Your ticket creates the request. Updates flow back.
API keys with read or read-and-write scope, signed webhooks for every change, and a delivery log, so your service desk and PeerToSite stay in step.
{
"site_code": "112",
"service_item_id": "…",
"urgency": "high",
"title": "Exit sign dark",
"description": "Exit sign dark, aisle 4",
"reference": "INC0012345"
}
Idempotency-Key: INC0012345
→ 201 {"id":"…", …}
webhook dispatch.accepted → your endpointWhat's in it
Integrations & API, in detail
REST API
Create a dispatch request from a ticket, read it, update it, comment in the job chat, cancel under the same rule as the button.
See itWebhooks
Every change queued in the same transaction, HMAC-signed, tried up to six times, with a delivery log you can read.
ServiceNow Not live yet
A connector that writes work notes on the ticket is built but switched off until it has been tested against a real ServiceNow instance. Until then, use the API and webhooks.
Keys you control
Named keys, read-only or read-and-write, last-used shown, 120 requests a minute per key. A key works only while its creator is an active Company Manager.
Payloads
What a webhook carries
The job, its status, times and site — never a technician's name or contact details. Send an Idempotency-Key and the request is created once, however often your system retries.
- dispatch.requested, accepted, checked_in, signed_off, completed, canceled…
- Public https endpoints only, no redirects
- Secrets encrypted at rest
{
"site_code": "112",
"service_item_id": "…",
"urgency": "high",
"title": "Exit sign dark",
"description": "Exit sign dark, aisle 4",
"reference": "INC0012345"
}
Idempotency-Key: INC0012345
→ 201 {"id":"…", …}
webhook dispatch.accepted → your endpointQuestions
Things people ask
Is the ServiceNow connector live?
It's built and tested against a stand-in, not yet against a real instance. It's switched off on the deployed site until that test is done.
Can I post opportunities by API?
Not fully. The API reads postings and can save a draft posting; publishing it, comparing bids and awarding happen in the app.
Who answers for our data in our ticket system?
Your company does: connecting a key or a webhook needs a responsibility tick, recorded in the audit log.
See it with your own sites
A 20-minute walkthrough with a real request.