Agentic Fabriq
Givebutter
BUSINESS · COMMERCE & FINANCE
Campaigns, contacts, transactions and payouts under that person’s own token.
Connecting Givebutter in practice
Givebutter allows 500 requests a minute but pages with 1-indexed offset pagination at 20 items by default and 100 at most, so pulling a year of transactions is hundreds of sequential calls against a limit that cannot be parallelised away. A key that authenticates fine still returns 403 for anything outside the organization it was issued in.
Rate limits
- 500 requests per minute, after which the API returns 429.
- 429 responses carry a Retry-After header stating how many seconds to wait.
- Paginated endpoints: per_page defaults to 20 with a maximum of 100; asking for more is an error.
Worth knowing
- Pagination is offset-based with 1-indexed page numbers and a links object; Givebutter’s advice is to "keep following next until it becomes null", so total page count is not known up front.
- A valid key can still receive 403 because it lacks permission for the resource or is "trying to access another organization’s data" — so 403 here is a scoping signal, not a bad credential.
- Keys are created in Settings → Integrations → API Keys and shown once: "your API key is shown only once", so an agent’s credential can be replaced but never re-read.
Checked against Authentication (2026-09-29), Rate limits (2026-09-29), Pagination (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Givebutter behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.