Share via

GET /v1.0/engagements/referrals returns 200 with 0 results after March 2026 QRP migration - was working April 2nd

Atharva Agate 0 Reputation points
2026-04-07T06:36:34.04+00:00

The Partner Center Referrals API (GET /v1.0/engagements/referrals) started returning 200 with 0 results sometime between April 2 and April 7, 2026. Data is clearly visible in the Partner Center portal under Co-sell opportunities.

What we verified:

  • Auth is working — invalid token returns 401, valid token returns 200
  • Role is Referrals Admin (Entire organization)
  • All OData filters tested: status, substatus, direction, type — all return 0
  • Tested via raw curl (not a code issue)
  • Setup matches the documentation exactly

Raw curl response:

{"@odata.context":"http://10.0.0.6:8833/v3/$metadata#Referrals","@odata.count":0,"value":[]}

Observations:

  • The @odata.context in the response leaks an internal IP (10.0.0.6:8833) on a v3 backend — not v1.0
  • Browser network inspection shows the Partner Center portal now calls api.partnercenterreferrals.microsoft.com — an undocumented domain, not accessible externally (returns AADSTS500011)
  • The previously working endpoint api.partnercenter.microsoft.com/v1/referrals now returns 500 (Activity ID: eabedc62-6e8d-48f8-aa64-13f48ea17ae7)

Question: Was the v1.0/engagements/referrals API affected by the QRP migration in March 2026? Is there a new documented endpoint for programmatically accessing co-sell opportunities?The Partner Center Referrals API (GET /v1.0/engagements/referrals) started returning 200 with 0 results sometime between April 2 and April 7, 2026. Data is clearly visible in the Partner Center portal under Co-sell opportunities.

What we verified:

  • Auth is working — invalid token returns 401, valid token returns 200
  • Role is Referrals Admin (Entire organization)
  • All OData filters tested: status, substatus, direction, type — all return 0
  • Tested via raw curl (not a code issue)
  • Setup matches the documentation exactly

Raw curl response:

{"@odata.context":"http://10.0.0.6:8833/v3/$metadata#Referrals","@odata.count":0,"value":[]}

Observations:

  • The @odata.context in the response leaks an internal IP (10.0.0.6:8833) on a v3 backend — not v1.0
  • Browser network inspection shows the Partner Center portal now calls api.partnercenterreferrals.microsoft.com — an undocumented domain, not accessible externally (returns AADSTS500011)
  • The previously working endpoint api.partnercenter.microsoft.com/v1/referrals now returns 500 (Activity ID: eabedc62-6e8d-48f8-aa64-13f48ea17ae7)

Question:
Was the v1.0/engagements/referrals API affected by the QRP migration in March 2026? Is there a new documented endpoint for programmatically accessing co-sell opportunities?

Microsoft Partner Center API
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-04-07T06:36:48.7966667+00:00

    The available documentation still shows GET https://api.partner.microsoft.com/v1.0/engagements/referrals as the supported public API to list leads and co-sell opportunities, and there is no documented replacement endpoint for programmatic access to co-sell opportunities.

    The documented behavior for that API remains:

    GET https://api.partner.microsoft.com/v1.0/engagements/referrals

    with optional OData parameters such as $select, $filter, and $orderby (for example, filtering by status, qualification, customerProfile/address/country, or direction, and ordering by createdDateTime or updatedDateTime).

    The context does not document any QRP-related change, deprecation, or migration of this endpoint, nor does it document api.partnercenterreferrals.microsoft.com as a public API surface. The only other referrals-related API in the provided material is the separate Partner Referrals endpoint for AI Business Solutions & Security Insights:

    GET https://m365partner.microsoft.com/abss/v1.3/api/partnerReferrals

    which is scoped to “any referrals currently being offered to your account” in that specific insights experience and is not documented as a general replacement for the Partner Center Referrals API or as a co-sell opportunities feed.

    Given the absence of any documented new endpoint or migration path in the provided material, and because the current documentation still points to https://api.partner.microsoft.com/v1.0/engagements/referrals for co-sell and lead retrieval, the issue described (HTTP 200 with empty results, internal @odata.context host, and 500s on the older v1/referrals URL) appears to be a service-side or platform issue rather than an intentional, documented API change.

    The only explicit forward-looking change in the context related to referrals/co-sell is around “smarter referral submissions” and UI workflow updates, not API surface changes. For production-impacting behavior like this, the documented escalation path is to open a support ticket through Partner Center Support so the engineering team can investigate the backend behavior and confirm whether any undocumented migration or regression is involved.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.