Pull Pike13 business data for dashboards with the Reporting API
domain: developer.pike13.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the same OAuth2 access token used for the Core API
Send requests to the Reporting API v3 endpoints to retrieve and aggregate business data
Respect the Reporting API's lower rate limit versus the Core API when scheduling batch pulls
Page through large report results using the documented pagination parameters
Cache results locally for dashboards rather than re-querying on every page load
Known gotchas
The Reporting API is rate-limited to roughly 60 requests per minute per IP or token, well below the Core API's 180/min, so jobs hitting both APIs can exhaust the budget faster than expected
Reporting API responses are aggregate/report-shaped, not the same resource objects returned by the Core API, so code written against Core API schemas needs separate parsing logic
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?