Overview
In the iFoodDS Trace Exchange program you can share FDA FSMA 204 key data elements (KDEs) with the iFoodDS API. iFoodDS aligns with the FDA FSMA 204 KDEs for the identified Critical Tracking Events (CTEs), specifically supporting the Shipping, Receiving, Transformation, First Land Based Receiver and Initial Packing FSMA 204 CTEs.
Getting started
You must have a signed agreement with iFoodDS to get your API Key. To access your API Key, log into your iFoodDS account and go to the Data Management section. If you do not see an API tab in your navigation, contact your account administrator to get access. Generated API Keys will expire in 180 days.
Once you've obtained an API key, we recommend storing it securely in a password vault, as we cannot recover it for you.
To consume any of the iFoodDS API endpoints, you must pass a valid API key in the header:
X-Api-Key: <api key>
You will receive a 403 Forbidden response if you use the key on an endpoint to which it does not have access. That is, a Customer API key cannot be used on a Data Provider endpoint, and vice versa. The key you generate is based on your account type.
Environments
The sandbox environment allows you to test your integrations without affecting production data. The base URL for the iFoodDS sandbox is as follows:
https://api-sandbox.ifoodds.com/api/v1
The URL below is for the iFoodDS Production environment. To avoid affecting production data, please ensure you're using the Sandbox URL above when testing your integration.
https://api.ifoodds.com/api/v1
Want to learn more about GS1?
Click Here to learn more about GS1.