Forum Discussion

cmjr86's avatar
cmjr86
Copper Contributor
Jul 22, 2026

Feature Request — Programmatic (API) access to Eligible/Ineligible Revenue data

Hi Product Team,

 

We're building an automated backend pipeline to ingest and reconcile our incentive and revenue data across multiple Microsoft programs (MCI/Co-Op), and we've hit a gap we'd like to flag for future roadmap consideration.

 

**Current situation**

The Partner Payout API (api.partner.microsoft.com/v1.0/payouts) already gives us solid programmatic access to Earnings and Payments exports, which we use successfully today. However, the Eligible/Ineligible Revenue data available on the Earnings > Revenue page in Partner Center has no equivalent API endpoint — it's currently only accessible via manual UI download.

 

We confirmed this with Commercial Marketplace Support (Service Request #2607220040003782), who kindly clarified that this is a known product limitation rather than a support/configuration issue, and suggested we raise it here directly with the Product Team.

 

**Business impact**

Without API access to this dataset, we're forced to rely on a manual, human-driven download step in an otherwise fully automated ingestion pipeline. This creates:

- A recurring operational dependency on a person manually exporting and uploading the file on a schedule

- A gap in our audit trail, since manual downloads are harder to log and timestamp consistently than API-driven exports

- Reconciliation delays between Eligible/Ineligible Revenue and the Earnings/Payments data we already pull automatically via API

 

**Request**

We'd like to ask the Product Team to consider extending the existing Payout API (or a comparable endpoint) to support an asynchronous export request for Eligible/Ineligible Revenue data, following the same pattern already used for Earnings and Payments (create export request → poll status → download via secure blob link).

 

Happy to share more detail on our use case if it's helpful for prioritization. Thank you for considering this.

 

Regards,

Carlos Rodrigues