Read recurring donation schedules for a Qgiv form via the Recurring Transactions API
domain: qgiv.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a form-scoped API token
Query the Recurring API to read existing recurring donation schedules tied to that form
Cross-reference recurring transaction IDs with corresponding one-time transaction records for full donor history
Apply report-mapping configuration if custom field values need to flow through in the recurring data output
Poll on a schedule, since the Recurring API is documented as a read/reporting interface
Known gotchas
The Recurring API is documented as a reporting/read interface — verify write support explicitly before assuming you can modify a schedule the same way you read it
Data is scoped to a single form's API token, so multi-form recurring reporting requires multiple calls and manual aggregation
Correct interpretation of Qgiv's field-type reference matters for parsing custom recurring donation fields
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?