This API exposes unemployment data for New York City, sourced from the Bureau of Labor Statistics. Developers can retrieve comprehensive data sets encompassing seasonally adjusted. The API returns data in JSON format, structured as tables with rows representing time series data (monthly from 2015 onwards). The response will be a JSON object with a nested array of data points, providing a structured and readily usable dataset for analysis and application integration. Data schemas are consistent, with clear labeling and data types for all fields, making data parsing straightforward.
{
"years_extracted": [
2015,
2016,
2017,
2018,
2019,
2020,
2021,
2022,
2023,
2024,
2025
]
}
curl --location --request POST 'https://zylalabs.com/api/8307/new+york+unemployment+data+fetch+api/14432/get+years+with+unemployment+data' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{
"year": 2025,
"month": "January",
"unemployment_rate": 3.7
}
curl --location --request POST 'https://zylalabs.com/api/8307/new+york+unemployment+data+fetch+api/14437/get+unemployment+rate+by+year+and+month' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"Required","month":"Required"}'
{
"year": 2018,
"average_unemployment_rate": 4.4
}
curl --location --request POST 'https://zylalabs.com/api/8307/new+york+unemployment+data+fetch+api/14441/get+average+unemployment+rate+by+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"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 unemployment rate data for New York City, sourced from the Bureau of Labor Statistics, including seasonally adjusted figures.
The API returns data in JSON format, structured as tables with rows representing monthly time series data from 2015 onwards.
Developers can use the API to build applications that analyze unemployment trends, create visualizations, or integrate unemployment data into economic reports.
The API response includes fields such as the unemployment rate, date, and other relevant metadata, all clearly labeled for easy parsing.
Developers can easily integrate the API by making HTTP requests to retrieve the structured JSON data, which can then be used in various applications for analysis or reporting.
This endpoint returns a list of years for which unemployment rate data is available in New York City, allowing users to identify the range of data they can query.
Users must specify both a year and a month (from January to December) as parameters to retrieve the corresponding unemployment rate for that specific time.
The response is structured as a JSON object containing the specified year and its corresponding average unemployment rate, making it easy to interpret and use in applications.
The response includes the fields "year," "month," and "unemployment_rate," providing clear information about the unemployment rate for the specified month and year.
Users can customize requests by selecting specific years and months when querying unemployment rates, allowing for tailored data retrieval based on their needs.
This endpoint provides the average unemployment rate for a specified year, enabling users to analyze trends over time and compare different years' economic conditions.
The API sources its data from the Bureau of Labor Statistics, ensuring high accuracy and reliability, as this organization is a trusted provider of labor market information.
Typical use cases include economic analysis, trend visualization, academic research, and integration into financial applications to assess labor market conditions in New York City.
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:
7,563ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
21ms
Service Level:
100%
Response Time:
10,320ms
Service Level:
100%
Response Time:
7,141ms
Service Level:
100%
Response Time:
61ms
Service Level:
33%
Response Time:
1,374ms
Service Level:
33%
Response Time:
6,060ms
Service Level:
33%
Response Time:
8,330ms
Service Level:
60%
Response Time:
8,084ms
Service Level:
100%
Response Time:
314ms
Service Level:
100%
Response Time:
346ms
Service Level:
100%
Response Time:
20ms
Service Level:
100%
Response Time:
295ms
Service Level:
100%
Response Time:
19ms
Service Level:
100%
Response Time:
1,545ms
Service Level:
100%
Response Time:
379ms
Service Level:
100%
Response Time:
1,535ms
Service Level:
100%
Response Time:
1,884ms
Service Level:
100%
Response Time:
16ms