Quickstart

1. Generate an API key

In the admin console, open Developer → API Keys and click Generate Key. Pick scopes matching what you plan to do — at minimum equipment:read for this quickstart (and groups:write for step 4). Copy the key; it's shown once.

2. No org ID needed

A key belongs to one organization, and every request made with it is scoped to that organization. The API never reads X-Org-Id on an API key request, so you don't send it.

3. Make a request

curl -s https://api.prestartgo.com/api/v1/equipment \
  -H "Authorization: Bearer psg_live_..." \
  -H "Accept: application/json"

A successful response:

{
  "success": true,
  "data": [
    { "id": "…", "serialNumber": "FRG-001", "status": "ACTIVE", "..." }
  ],
  "meta": { "limit": 20, "hasMore": true, "nextCursor": "eyJpZCI6IjEyMyJ9" }
}

4. Make a mutation (with idempotency)

Every non-GET request needs an Idempotency-Key header (a fresh UUID v4):

curl -s -X POST https://api.prestartgo.com/api/v1/groups \
  -H "Authorization: Bearer psg_live_..." \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Excavators" }'

Retrying the exact same body with the same Idempotency-Key returns the same result without re-creating the resource.

Next steps

• Authentication — the full scope catalogue.
• Errors — what to do when something fails.
• Rate limits — tier quotas and Retry-After.
• Webhooks — push events instead of polling.