approvals.list
Approval requests for a shop, newest first, optionally by status (pending, approved, denied, failed, expired). Requests past their expiry read as expired. Owner and office see every request; a field worker sees only the ones they or their agents asked for.
| Who | Agents can call this |
| REST | GET /v1/approvals |
| MCP tool | approvals_list |
| Writes | no |
| Area | Team (unlimited workers) |
When to use it
An owner can say which actions an agent must ask about first, optionally only above an amount. When a rule matches, your call returns an approval id instead of running.
What to tell the owner
Tell them what you found in plain words. Don't read back raw fields.
Input
| Field | Type | Required |
|---|---|---|
shop_id | string (uuid) | yes |
status | string (one of pending, approved, denied, failed, expired) | no |
Example
GET https://doingwork.work/v1/approvals?shop_id=00000000-0000-4000-8000-000000000000Output
JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.
Errors
| Code | Status | What to do |
|---|---|---|
invalid_input, invalid_token, rate_limited | Can happen on any call. See errors. |