Changelog2026

New Legacy Report ID Map Endpoint

We added a new endpoint to help integrations transition from legacy custom reports to our updated reporting infrastructure.

Get Legacy Report ID Map (GET /api/v1/custom-reports/legacy-id-map) returns a mapping from legacy custom report IDs to the new IDs created by report migration. If your integration or automation still references legacy report IDs, use this endpoint to look up the migrated ID, then pass that newReportId to Get Report by ID to run the migrated report.

Key details:

  • Each mapping pairs a legacyReportId with its newReportId and a status of migrated or notMigrated. When a report hasn't been migrated, newReportId is null.
  • Administrators receive mappings for every custom report in the company. Other users receive mappings only for reports they own or that are shared with them, so for non-admins, a missing legacy ID may simply be outside that user's visibility rather than nonexistent.
  • The endpoint returns a 403 when the user doesn't have permission to access reports at all. If the user has reports access but no legacy reports they owned or that were shared with them before migration, it returns a 200 with an empty mappings array.
  • Supports both Basic Auth and OAuth 2.0 with the report scope.

Full documentation is available under Get Legacy Report ID Map.