- Payments export: create a payments export request for a date range and payout status, then read it back until the download link appears
- Transaction history export: the same request–poll pattern for the earnings transactions behind each payment, with programme and lever filters
- Housekeeping: delete a payments or transaction-history export request once the file has been fetched
- Six routes (two read-only) on api.partner.microsoft.com, documented in the AI integration guide (llms.txt)
Microsoft Partner Center Payouts API Connector
Microsoft Partner Center Payouts API — request asynchronous exports of your partner payment history and transaction history, poll each export until the file is ready, and delete finished requests — registered in Apivom Atlas as six routes for Microsoft partners reconciling incentives and marketplace earnings.
What you can do
Use cases
- Monthly payout reconciliation — Export each month's payments and transaction history, load them into your finance system and match every payout line to the customer deal or incentive that earned it.
- Earnings per customer in the CRM — Join transaction-history rows to CSP customers so account managers see which accounts actually generate marketplace and incentive revenue.
Partner Center shows Microsoft partners what they have earned — incentives, commercial-marketplace sales, Cloud Solution Provider rebates — and what has been paid out, and the Payouts API makes that data exportable. It is deliberately small and asynchronous: you create an export request for payments or for transaction history, with a date range and optional filters on payout status, programme or earning lever; Microsoft prepares the file in the background; you poll the request by id until the status is complete and a download link is returned; and you delete the request afterwards. Apivom Atlas registers all six routes with the credential contract (an Entra app registration in the partner tenant, token audience api.partner.microsoft.com) and the AI integration guide (llms.txt), logging every call per tenant. No Apivom product workflow uses the Payouts API today — Apivom's own partner-licensing automation is built on Autodesk, not Microsoft — so the connector is available to Microsoft partners who want payout data in their finance or CRM systems, with a product workflow scoped per customer.
Entra token for the partner tenant: tenant id, app registration client id + secret, exchanged by the caller at login.microsoftonline.com/{tenantId}/oauth2/token (resource api.partner.microsoft.com), sent as Bearer per request. Secret encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Can I switch this connector on today?
The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.
Why are there only six routes?
Because the API is an export service, not a query API. Payments and transaction history each have create, read and delete on an export request; the data itself arrives as a downloadable file once the request completes.
Which permissions does the app registration need?
An app registration in your partner tenant with access to Partner Center, consented by a user who holds a payout-related role (such as Account admin or Incentive admin). The token audience is api.partner.microsoft.com, not the main Partner Center API host.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.