The midíadía API provides access to nutritional data from thousands of packaged products, allowing developers to create websites and apps that quantify and display relationships between product recipe information. The data could be used for developing applications that help manage special dietary restrictions, such as allergies and intolerances, as well as for optimizing nutrition. The API is well documented through Apiary.com, and uses HTTP requests that accept the JSON protocol. Developers interested in consuming the midíadía API need an API secret key for authorization, which can be obtained through signing up through the midíadía service.
This API gives you access to data across thousands of packaged products; use this API to build sophisticated websites and apps to display extended information, relationships between products and recipes and suitability with a user profile.
Apps made using midíadía’s API can help end users manage any specialist diet, including allergies, intolerances, optimal nutrition & more.
All responses from this API will be returned in JSONformat. The error responses will be returned as HTTP errors.
In order to correctly integrate with our system it's necessary to obtain the API Key from the system. If you don't currently have the Key you can get one by signing up to the service at (http://api.midiadia.com).
All requests must be authorized with a valid API secret key. Test API key just retrieve 3 results per method.
Always be careful never to publish your API secret key as it uniquely identifies your account and will allow anyone with your API key to gain access to your account.
midíadía uses conventional HTTP status codes to indicate success or failure of API requests. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that resulted from the provided information (e.g. a required parameter was missing), and codes in the 5xx range indicate an error with midíadía′s servers. You are most likely to come across one of the following errors:
400 (Bad Request): Your JSON request was either of invalid format or was not URL encoded.
401 (Unauthorized): You failed to authenticate.
429 (Too Many Requests): Your request was throttled.
500 (Internal Server Error): Error with midíadía′s servers.