Skip to main content
To implement API calls with Global-e the only required information is the merchantGUID provided by Global-e. For authentication, make sure to include your Merchant GUID as part of each call or as part of the header so that Global-e can verify your identity. Make sure to use the appropriate merchantGUID, depending on the Global‑e integration environment used for development or production purposes. See Global-e Environments. MerchantGUID in URL Add your MerchantGUID as part of each API URL. MerchantGUID as part of the header Add your MerchantGUID as part of the header as illustrated below.

Rotating Your Merchant GUID

Your Merchant GUID is the credential that identifies your store to Global-e, so it should be treated as a secret and replaced periodically, just as you would rotate any other API credential. Follow the instructions for your platform below to rotate your Merchant GUID:

IP Whitelisting

As part of strengthening the security of the integration between your systems and Global-e, we recommend whitelisting the IP addresses that access our APIs, so that only traffic from your approved infrastructure can access your Global-e account. As part of your integration, please provide the full list of public IP addresses (or CIDR ranges) that you use to connect to Global-e. The required list may include every system and application with an interface to Global-e:
  • Production servers and any backend calling Global-e APIs
  • OMS, ERP or middleware that syncs orders, catalog, product feeds or returns
  • Warehouse, 3PL or WMS systems that handle shipping activities
  • Integration partners or agencies acting on your behalf
  • Staging or test environments, marked as such
When your IP addresses change in the future, please notify us before the change.
Any system that is not whitelisted may be prevented from accessing Global-e systems and performing expected operations.