List shifts
/shiftsReturns your shift patterns, sorted by name. Shift times are local times in the site's time zone. Agoo uses them, with the grace period, to decide who is late.
Scope: attendance:read · Plan: Pro and Enterprise in live mode; every plan in test mode.
Send Authorization: Bearer <token> on every request. The token is one of:
| Prefix | What it is | Where it may be used |
|---|---|---|
agoo_sk_live_ | Secret key, live mode | Your servers only |
agoo_sk_test_ | Secret key, test mode | Your servers only |
agoo_pk_live_ | Publishable key, live mode | Browsers and apps: create pre-registrations and bookings, read public booking types (with their intake questions) and their free slots, read the visit types open for pre-registration with their public forms. Never lists people. |
agoo_pk_test_ | Publishable key, test mode | As above, in test mode |
Admins create keys in Console → Developers → API keys and choose each key's scopes. A key is shown once. Never put a secret key in a URL, a browser or a mobile app.
In: header
Scope: attendance:read
Query Parameters
How many items to return, from 1 to 100.
1 <= value <= 10025The next_cursor from the previous page. Leave it out for the first page.
length <= 512Only shifts at this site.
^site_[0-7][0-9a-hjkmnp-tv-z]{25}$"site_01kjpt3yw0fz0v414608h9x65s"Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X GET "https://example.com/shifts?limit=25"{ "data": [ { "id": "shift_01kn6pqfm0fmasbh61jnr3syze", "name": "Day shift", "site_id": "site_01kjpt3yw0fz0v414608h9x65s", "start_time": "08:00", "end_time": "17:00", "days": [ "mon", "tue", "wed", "thu", "fri" ], "grace_minutes": 5, "created_at": "2026-04-02T09:00:00Z", "updated_at": "2026-04-02T09:00:00Z" } ], "next_cursor": null, "has_more": false}Get an attendance summary GET
Counts, for each day in a range, how many people on attendance were present, late, on leave or absent. Each person counts once per day, in exactly one of the four. Days are whole days in the site's time zone (or your organisation's, without `site_id`). The range can span up to 31 days. **Scope:** `attendance:read` · **Plan:** Pro and Enterprise in live mode; every plan in test mode.
Review a punch whose face wasn't verified POST
Accepts or rejects a fallback punch (PIN, QR, NFC or supervisor-assisted) after a failed face match: its `face_check` is `not_verified` and its `review.status` is `pending`. These punches form the review queue (`GET /attendance/events?review_status=pending`) and are counted in the summary until reviewed. - `accepted` keeps the punch. `rejected` voids it: it no longer appears or counts. - A punch that isn't awaiting review returns `invalid_state`. **Scope:** `attendance:manage` · **Plan:** Pro and Enterprise in live mode; every plan in test mode.