The Historical Food Price Records API is designed to handle the domain of agricultural commodities, specifically focusing on food price indices. It processes a variety of data fields including commodity types, historical price values, and indices for different food categories such as grains, meats, fruits, and beverages. The API utilizes domain-specific terminology such as 'Commodity Food Price Index' and 'Commodity Agricultural Raw Materials Index', adhering to established standards for commodity pricing. Data is structured in a JSON format, with fields for commodity name, price, date, and index type, allowing for easy integration and analysis. Technical requirements include secure access protocols and adherence to data accuracy standards, ensuring reliable information retrieval. The output schema is designed to provide clear and concise data, facilitating users' ability to analyze trends over time and make informed decisions based on historical price movements.
[
{
"Aug 2002": 61.5
}
]
curl --location --request POST 'https://zylalabs.com/api/10227/historical+food+price+records+api/19669/get+historical+food+commodity+price' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"month":"Required","year":"Required"}'
[
{
"Month": "Aug 2002",
"Price": "61.50",
"Change": "-0.18%"
}
]
curl --location --request POST 'https://zylalabs.com/api/10227/historical+food+price+records+api/19672/get+historical+food+commodity+price+change' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"date_1":"Required","date_2":"Required","date":"Required"}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The API provides historical price indices for various food commodities, including grains, meats, fruits, and beverages. It includes data fields such as commodity name, price, date, and index type.
The data is structured in a JSON format, which allows for easy integration and analysis. Each data entry includes fields for commodity name, price, date, and index type.
Users can leverage the API to track market trends and fluctuations in food commodity prices, conduct historical analysis for research, and make informed decisions in agricultural investments or pricing strategies.
The core value proposition lies in its ability to provide reliable and accurate historical price data for food commodities, enabling users to analyze trends over time and make data-driven decisions.
The output schema includes fields such as 'commodity name', 'price', 'date', and 'index type', allowing users to easily access and analyze relevant information regarding food commodity prices.
This endpoint returns historical food commodity prices for a specified month and year, allowing users to access price data from August 1995 to the present. The response includes the commodity name and its corresponding price for the requested date.
The response includes fields such as "Month," "Price," and "Change." "Month" indicates the specific month and year, "Price" shows the commodity price, and "Change" reflects the percentage change from the previous period.
The response data is structured in a JSON format, with each entry containing key-value pairs. For example, the "get historical food commodity price" endpoint returns an object with the month as the key and the price as the value, facilitating easy data parsing.
Users can specify the month and year as parameters when making requests to both endpoints. For example, to retrieve data for August 2002, users would include "month" and "year" parameters in their request.
This endpoint provides information on historical price changes for food commodities, including the price for a specific month, the percentage change compared to the previous month, and the month/year of the data.
Users can analyze trends in food commodity prices over time, compare price changes across different commodities, and incorporate this data into reports or decision-making processes related to agriculture and market strategies.
The API sources its data from established agricultural commodity pricing standards and databases, ensuring that the information is reliable and relevant for users seeking historical price records.
Data accuracy is maintained through rigorous quality checks and adherence to established standards for commodity pricing. This includes regular updates and validation against trusted agricultural data sources.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
59ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
59ms
Service Level:
100%
Response Time:
4,783ms
Service Level:
100%
Response Time:
5,607ms
Service Level:
100%
Response Time:
2,374ms
Service Level:
100%
Response Time:
6,078ms
Service Level:
100%
Response Time:
5,599ms
Service Level:
100%
Response Time:
1,725ms
Service Level:
100%
Response Time:
102ms
Service Level:
100%
Response Time:
187ms
Service Level:
100%
Response Time:
123ms
Service Level:
100%
Response Time:
81ms
Service Level:
100%
Response Time:
157ms
Service Level:
100%
Response Time:
196ms
Service Level:
100%
Response Time:
132ms
Service Level:
100%
Response Time:
269ms
Service Level:
100%
Response Time:
572ms
Service Level:
100%
Response Time:
107ms