JobsiteOn

API Access and Webhooks

Use scoped Capture API tokens, find the API reference, and verify webhook deliveries.

Ethan Rivera
Written by Ethan RiveraUpdated over a week ago2 min readAdvanced

Availability

Capture API access and webhook setup are currently unavailable. The reference below describes the API contract for enabled deployments. A plan upgrade does not turn it on. The MCP/AI Connector has separate availability and setup instructions.

API address

JobsiteOn's public API uses https://api.jobsiteon.com. The supported Capture API base is https://api.jobsiteon.com/api/capture/v1.

Use the OpenAPI reference for the current endpoints, request fields and required scopes. You can also import the Postman collection.

Create a token

Owners and admins can open Settings → Capture → API & webhooks to create a personal access token. Choose only the scopes the integration needs. Copy the token when it appears, since it is shown once.

Tokens belong to either Sandbox or Live. Start in Sandbox and send the token in an HTTPS request header:

Authorization: Bearer your_token

Keep tokens on your server. Don't put them in a URL, browser code or a public repository. Revoke a token immediately if someone else may have it.

Requests and retries

Lists use cursors and return { data, pagination }. Write requests require an Idempotency-Key. Keep the same key when retrying the same write so it cannot create duplicate work. A different write needs a different key.

If the API returns 429, pause before retrying. Read the response's rate limit headers and the API reference instead of assuming a fixed limit.

Webhooks

Open Settings → Capture → API & webhooks to choose events and add your HTTPS endpoint. The endpoint's signing secret is separate from your API token. Verify the timestamp and HMAC-SHA256 signature before processing a delivery.

Capture API and Webhooks explains signature verification, secret rotation, supported events and failed deliveries.

AI assistants

To connect Claude or another supported assistant, use the MCP/AI Connector. It uses an authorization flow and workspace permissions, so you don't paste a Capture API token into an assistant.

Did this answer your question?

Related Articles