Use the four HTTP resources
The HTTP route accepts campaigns, submissions, payouts and deposits. Campaigns include budget and status. Submissions include submitted posts and verified-view fields. Payouts describe recorded payment stages. Deposits returns top-up fee lines with their associated deposit amounts; it is not one row per top-up.
Treat since as a creation filter
The current route defaults to 50 records and caps a request at 200. since filters campaign creation, submission time, payout request time or fee-record creation, depending on the resource. It is not an updated-since feed. An older payout changing status can be absent from a newer-time query.
- Choose the resource and a valid ISO timestamp when filtering.
- Record the request's scope and returned count with your report.
- Label bounded results as a sample when you cannot establish completeness.
- Use the dashboard's records view or ask about export needs when you need a complete history.
Do not sum repeated deposit amounts
Several fee lines can refer to the same deposit amount. Summing deposit_amount across the deposits response can overstate wallet funding. The response does not provide a complete transaction ledger, research feed, engagement analytics export or cursor pagination. Do not manufacture those products from an incomplete response.
Common questions
Can I increment since until I have every record?
No. Newest-first bounded results and a since filter do not supply backward cursor pagination. A full batch can hide older matches, and timestamp ties need additional handling that this route does not expose.
Need a hand?
Use Feedback in your dashboard if a guide does not answer your question. Include the page, what you expected and what happened. Never include a password, API key, account number or private payload.
Open API & connections