Market-specific to Global API mapping

Introduction

Use the Global partner API market capability mapping spreadsheet to understand how market-specific legacy Marketplace APIs map to the Global partner APIs, and to identify capabilities that are available only in the Global APIs. Always refer to the latest version of the spreadsheet. Use it as the source of truth for mapping decisions.

Global Partner API - Market Capability Mapping

When this is useful

• Planning a migration from market-specific integrations to Global Partner APIs
• Determining whether you can standardize your integration across markets
• Identifying Global capabilities you can add (even if you don’t use a legacy equivalent today)

What’s in the spreadsheet

The workbook is organized by market and includes:

• Market-specific API details: API name, method, path
• Global mapping: The equivalent Global API name/path when available
• Availability indicator: whether a legacy API is available in Global
• Global-only capabilities: a dedicated section/tab that lists APIs/capabilities introduced in Global with no legacy equivalent

How to use it

1. Pick your market tab (for example, US, CA, MX, CL).

2. Find the legacy endpoint you use today.

3. Check whether it is available in Global:

   • If Yes, use the mapped Global API listed in the mapping columns.
   • If No, treat it as market-only and plan for market-specific integration where needed.

4. Review the Global-only section to identify new capabilities you can adopt when moving to Global.

Notes and limitations

The mapping is intended as a functional reference. In some cases, the Global API may differ in:

• request/response shape
• required headers/parameters
• supported workflows and feature flags by market