Daily RevedUp ping reporting through the Public API
Category: Feature
Location: Public API → GET /api/v1/revedup/ping-report
Release Date: October 21 2026
Retrieve a day’s RevedUp-enrolled campaign activity directly through the API, instead of assembling a daily ping report manually. This is for teams reconciling ping outcomes and RevedUp decisions in their own reporting tools.
What’s new
• Request one calendar day in a chosen timezone, with optional campaign and publisher filters.
• Review request and auction identifiers, campaign and publisher, sub-source, timestamps, location, requested duration and payout, route counts, bid amounts and auction outcomes.
• Include RevedUp decision details when a ping was scored, plus whether the associated call converted to billable.
• Retrieve large daily reports in pages of up to 1,000 rows using the returned cursor.
How to use it
• Use your organization’s Moja API key. If you need to retrieve it, open Admin → My Account → Profile → Moja API.
• Send a GET request to /api/v1/revedup/ping-report with date in YYYY-MM-DD format and your key in the X-API-Key header.
• Set timezone to an IANA timezone when needed; the default is America/New_York. Optionally supply campaign_id, publisher_id and limit from 1 to 1,000.
• When meta.has_more is true, repeat the request with meta.next_cursor as cursor, keeping the same day, timezone and filters.
Quick examples
• Reconcile yesterday’s enrolled-campaign pings against your own auction records using request and auction identifiers.
• Review one publisher’s daily bids and scored decisions, then fetch the remaining pages for that same reporting day.
Impact
• Automate daily reconciliation while keeping the report scoped to your organization and RevedUp-enrolled campaigns.
• Distinguish bid activity, auction outcome and billable conversion rather than treating them as the same event.
Important limitations
• Each request covers one calendar day, not a multi-day date range. A cursor cannot be reused with a different day or filter selection.
• downstream_payout currently returns 0; do not use it as a confirmed downstream-payment amount.
• Decision fields may be empty when no score is recorded. This endpoint does not create a missing decision or initiate a conversion upload.
