Including domain licenses in partner reports

Hi Developer Community,

Based on the feedback received during the rollout of the new reporting pipeline – we are now providing a query parameter, includeAtlassianLicenses, to enable partners to view internal Atlassian licenses. These licenses are used internally within Atlassian and were earlier being excluded from the reporting APIs.

The change is expected to be rolled out around Jan 31, 2023 .

Affected APIs

Partners can add the includeAtlassianLicenses=true query parameter to these APIs to include internal Atlassian licenses in the report.

Licenses API

  • GET /rest/2/vendors/{vendorId}/reporting/licenses
  • GET /rest/2/vendors/{vendorId}/reporting/licenses/export

API URLs for including Atlassian licenses:

  • GET /rest/2/vendors/{vendorId}/reporting/licenses?includeAtlassianLicenses=true
  • GET /rest/2/vendors/{vendorId}/reporting/licenses/export?includeAtlassianLicenses=true

Partners might see new historical licenses that appear when this parameter is provided.

Free Starter Tier API

  • GET rest/2/vendors/{vendorId}/reporting/sales/freeStarterTier/export

API URLs for including Atlassian licenses in free starter tier API:

  • GET rest/2/vendors/{vendorId}/reporting/sales/freeStarterTier/export?includeAtlassianLicenses=true

Partners might see new historical licenses that appear when this parameter is provided.


  • The Cloud churn and evaluations metrics API will not be affected by this change, i.e, the following APIs will not include internal Atlassian licenses.

    • cloud churn, renewal conversion APIs rest/2/vendors/{vendorId}/reporting/sales/metrics/churn|renewal|conversion,
    • cloud license events API rest/2/vendors/{vendorId}/reporting/sales/{metrics}/details and
    • aggregated evaluations API rest/2/vendors/{vendorId}/reporting/evaluation/{metrics}
  • The lastUpdated date in the licenses API will not be Jan 31, 2023 for these internal Atlassian licenses. Partners will need to do a one-time back-fill for their lifetime data to see historical internal Atlassian licenses.


Thanks for making this possible! We don’t care that much about those Atlassian licenses, but since they were being removed after a few days it makes our license code much easier if we no longer have to consider licenses being removed after initially being available. So the parameter is definitely helpful - thanks!

1 Like

Great news!

Is there a way to distinguish these licenses from a regular ones?
Maybe they have specific flag or field?

1 Like

Hey @lexek-92 - We don’t have a specific flag today. But you can identify it by looking at technical_email or billing_email field which should end with After the current release, we will explore the possibility of adding an additional flag if need be.

Hi Developer community - I wanted to let you know that the change is now live in production. You can now use the parameters mentioned in the note above to pull licenses. You can also find more details about the parameter in DAC( in the below links. Thanks!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.