Integration checklist

Check your scopes, request formats, and error handling before going live.

Before going live:

1. Confirm the token is a Core organization token and has not expired.
2. Confirm a scope exists for every resource your integration calls.
3. Confirm each event is inside the scope’s event selection.
4. Select only the response fields and associations the integration genuinely needs.
5. Select every filter the integration sends; unselected filters are ignored.
6. Configure row restrictions and test both an allowed and a disallowed record.
7. For writes, enable both the write permission and each required action, input, and write-response field.
8. Test pagination with more than 30 records.
9. Store timestamps with explicit time-zone offsets, preferably UTC (Z).
10. Handle 400, 403, 404, 422, and 429 distinctly and log Brella request context without logging the token.

When a response seems incomplete, compare it with the scope in this order: readable fields, event selection, row restrictions, query fields, included associations, and the caller’s include parameter. That sequence explains most differences without changing the API request itself.