Business-Day API

API ID 12996

Accurate business-day, holiday, and scheduling math for major countries and their subdivisions — without maintaining a single holiday calendar yourself. Add or subtract working days, check if a date is a business day, find the next valid date, or count working days between two dates, with full support for regional subdivisions, custom weekends, and your own blackout dates. One simple GET call, instant JSON.

203 ms avg response

API Documentation

Endpoints

Request

Checks whether a given date is a working business day for a country or region, accounting for weekends, public holidays, and any custom blackout dates you supply. Returns true or false. Supports regional subdivisions (e.g. US states, German Länder) and configurable weekend days for Friday/Saturday-weekend regions.

Endpoint ID: 26001
GET https://www.zylalabs.com/api/12996/business-day+api/26001/is+business+day
INPUT PARAMETERS

Is Business Day — Endpoint Features

Object Description
date Required Date to check, ISO format YYYY-MM-DD (e.g. 2026-12-25)
region Required ISO country code, e.g. US, GB, DE, CA
weekend Optional Optional weekend days, comma-separated Mon=0 to Sun=6. Default 5,6 (Sat/Sun). Use 4,5 for Friday/Saturday regions
extra_holidays Optional Optional comma-separated ISO dates to treat as non-working days
subdiv Optional Optional state/province/region code, e.g. CA for California or BY for Bavaria

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

date
region
weekend
extra_holidays
subdiv
API EXAMPLE RESPONSE
JSON
{"date":"2026-12-25","region":"US","is_business_day":false}
Is Business Day — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12996/business-day+api/26001/is+business+day?date=Required®ion=Required' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request

Adds or subtracts a number of working business days to a date, skipping weekends, public holidays, and any custom blackout dates. Supports regional subdivisions and configurable weekends.

Endpoint ID: 26002
GET https://www.zylalabs.com/api/12996/business-day+api/26002/add+business+days
INPUT PARAMETERS

Add Business Days — Endpoint Features

Object Description
date Required Date to check, ISO format YYYY-MM-DD (e.g. 2026-12-25)
days Required Number of business days to add. Use a negative number to subtract, e.g. 5 or -3
region Required ISO country code, e.g. US, GB, DE, CA
subdiv Optional Optional state/province/region code, e.g. CA for California or BY for Bavaria
weekend Optional Optional weekend days, comma-separated Mon=0 to Sun=6. Default 5,6 (Sat/Sun). Use 4,5 for Friday/Saturday regions
extra_holidays Optional Optional comma-separated ISO dates to treat as non-working days, e.g. 2026-07-06

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

date
days
region
subdiv
weekend
extra_holidays
API EXAMPLE RESPONSE
JSON
{"start":"2026-07-02","days":5,"result":"2026-07-10"}
Add Business Days — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12996/business-day+api/26002/add+business+days?date=2026-07-02&days=5®ion=US' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request

Returns the first working business day on or after a given date, skipping weekends, public holidays, and custom blackout dates. Set inclusive=true to allow the date itself if it is already a working day.

Endpoint ID: 26003
GET https://www.zylalabs.com/api/12996/business-day+api/26003/next+business+day
INPUT PARAMETERS

Next Business Day — Endpoint Features

Object Description
date Required Date to check, ISO format YYYY-MM-DD (e.g. 2026-12-25)
region Required ISO country code, e.g. US, GB, DE, CA
inclusive Optional Optional true or false. If true, returns the date itself when it is already a working day. Default false
subdiv Optional Optional state/province/region code, e.g. CA for California or BY for Bavaria
weekend Optional Optional weekend days, comma-separated Mon=0 to Sun=6. Default 5,6 (Sat/Sun). Use 4,5 for Friday/Saturday regions
extra_holidays Optional Optional comma-separated ISO dates to treat as non-working days, e.g. 2026-07-06

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

date
region
inclusive
subdiv
weekend
extra_holidays
API EXAMPLE RESPONSE
JSON
{"from":"2026-07-02","result":"2026-07-06"}
Next Business Day — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12996/business-day+api/26003/next+business+day?date=2026-07-02®ion=US' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request

Counts the number of working business days between two dates, excluding weekends, public holidays, and custom blackout dates. Supports regional subdivisions and configurable weekends.

Endpoint ID: 26004
GET https://www.zylalabs.com/api/12996/business-day+api/26004/business+days+between
INPUT PARAMETERS

Business Days Between — Endpoint Features

Object Description
start Required Start date in ISO format YYYY-MM-DD, e.g. 2026-07-01
end Required End date in ISO format YYYY-MM-DD, e.g. 2026-07-31
region Required ISO country code, e.g. US, GB, DE, CA
subdiv Optional Optional state/province/region code, e.g. CA for California or BY for Bavaria
weekend Optional Optional weekend days, comma-separated Mon=0 to Sun=6. Default 5,6 (Sat/Sun). Use 4,5 for Friday/Saturday regions
extra_holidays Optional Optional comma-separated ISO dates to treat as non-working days, e.g. 2026-07-06

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

start
end
region
subdiv
weekend
extra_holidays
API EXAMPLE RESPONSE
JSON
{"start":"2026-07-01","end":"2026-07-31","business_days":21}
Business Days Between — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/12996/business-day+api/26004/business+days+between?start=2026-07-01&end=2026-07-31®ion=US' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Business-Day API simply include your bearer token in the Authorization header.

Headers
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.

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Date arithmetic looks trivial until you cross a border. "Five business days from today" means something different in California than in Bavaria, observed-holiday rules shift weekends around, some regions don't even use a Saturday/Sunday weekend, and every customer has their own closures on top of the public calendar. Getting this wrong quietly breaks SLA clocks, delivery estimates, payment settlement windows, and appointment scheduling.

This API handles all of it behind one endpoint. Public holidays for over 100 countries and their subdivisions (US states, German Länder, Canadian provinces, and more) are kept current for you. On top of that you get the things a raw calendar can't do on its own: working-day arithmetic, configurable weekend days for non-Mon–Fri regions, and per-request custom holidays so a customer's own office closures fold into the calculation.

Built for logistics and delivery-date estimation, fintech settlement and payment scheduling, SLA and ticket-aging clocks, payroll, and any appointment or booking system that has to respect real working days. Responses are small, cacheable JSON and return in milliseconds.

Highlights

  • 100+ countries with regional subdivision support
  • Add / subtract business days, with correct observed-holiday handling
  • Check any date, find the next working day, or count working days in a range
  • Configurable weekends (e.g. Friday/Saturday regions)
  • Per-request custom holidays / blackout dates
  • Tiny JSON in, tiny JSON out — one GET call, no SDK required

Endpoint reference

All endpoints are GET. Dates are ISO YYYY-MM-DD. region is an ISO country code (e.g. US, GB, DE, CA). Optional params:

  • subdiv — state/province/region code (e.g. CA for California, BY for Bavaria)
  • weekend — comma-separated weekday numbers, Monday=0 … Sunday=6. Default 5,6 (Sat/Sun). Example: 4,5 for a Friday/Saturday weekend.
  • extra_holidays — comma-separated ISO dates to treat as non-working (a customer's own closures), merged with the public calendar.

1. Is business day — GET /v1/is-business-day

Returns whether a date is a working day (not a weekend, public holiday, or supplied blackout date).

Param Required Example
date yes 2026-12-25
region yes US
subdiv no CA
weekend no 5,6
extra_holidays no 2026-12-24

Request:

 
GET /v1/is-business-day?date=2026-12-25&region=US

Response:

 
json
{ "date": "2026-12-25", "region": "US", "is_business_day": false }

2. Add business days — GET /v1/add-business-days

Adds (or subtracts, if days is negative) N working days to a date.

Param Required Example
date yes 2026-07-02
days yes 5
region yes US
subdiv no CA
weekend no 5,6
extra_holidays no 2026-07-06

Request:

 
GET /v1/add-business-days?date=2026-07-02&days=5&region=US&subdiv=CA

Response:

 
json
{ "start": "2026-07-02", "days": 5, "result": "2026-07-10" }

(July 3 is the observed Independence Day holiday, plus two weekends, so five working days lands on July 10.)

3. Next business day — GET /v1/next-business-day

Returns the first working day after a date. Pass inclusive=true to allow the date itself if it is already a working day.

Param Required Example
date yes 2026-12-25
region yes US
inclusive no false
subdiv no CA
weekend no 5,6
extra_holidays no

Request:

 
GET /v1/next-business-day?date=2026-12-25&region=US

Response:

 
json
{ "from": "2026-12-25", "result": "2026-12-28" }

4. Business days between — GET /v1/business-days-between

Counts working days in the half-open interval (start, end]. Negative if end precedes start.

Param Required Example
start yes 2026-12-24
end yes 2026-12-31
region yes US
subdiv no CA
weekend no 5,6
extra_holidays no

Request:

 
GET /v1/business-days-between?start=2026-12-24&end=2026-12-31&region=US

Response:

 
json
{ "start": "2026-12-24", "end": "2026-12-31", "business_days": 4 }

Errors

  • 400 — bad input (malformed date, out-of-range weekend, unsupported region). Body: { "detail": "" }
  • 401 — missing or invalid key (handled by the marketplace layer).
  • 429 — rate limit exceeded.

International examples (demonstrate coverage, don't just claim it)

These show the regional parameters actually changing the result — the most credible thing a browsing developer can see. All values verified against the live calendars.

Subdivisions matter — same date, different answer

Epiphany (Jan 6, 2026, a Tuesday) is a public holiday in Bavaria but a normal working day in Berlin:

 
GET /v1/is-business-day?date=2026-01-06&region=DE&subdiv=BY
{ "date": "2026-01-06", "region": "DE", "is_business_day": false }

GET /v1/is-business-day?date=2026-01-06&region=DE&subdiv=BE
{ "date": "2026-01-06", "region": "DE", "is_business_day": true }

The arithmetic reflects it too — adding one working day to Wed June 3 skips Corpus Christi (Thu June 4) in Bavaria, but not in Berlin:

 
GET /v1/add-business-days?date=2026-06-03&days=1&region=DE&subdiv=BY
{ "start": "2026-06-03", "days": 1, "result": "2026-06-05" }

GET /v1/add-business-days?date=2026-06-03&days=1&region=DE&subdiv=BE
{ "start": "2026-06-03", "days": 1, "result": "2026-06-04" }

Non-Mon–Fri weekends

Egypt with a Friday/Saturday weekend — one working day after Thursday March 5 lands on Sunday March 8, not Friday:

 
GET /v1/add-business-days?date=2026-03-05&days=1&region=EG&weekend=4,5
{ "start": "2026-03-05", "days": 1, "result": "2026-03-08" }

GET /v1/next-business-day?date=2026-03-05&region=EG&weekend=4,5
{ "from": "2026-03-05", "result": "2026-03-08" }

Counting working days under a Friday/Saturday weekend (Saudi Arabia, Mar 1–8):

 
GET /v1/business-days-between?start=2026-03-01&end=2026-03-08&region=SA&weekend=4,5
{ "start": "2026-03-01", "end": "2026-03-08", "business_days": 5 }

Region changes the holiday set

July 3, 2026 is the observed US Independence Day holiday, but an ordinary working day in the UK:

 
GET /v1/is-business-day?date=2026-07-03&region=US
{ "date": "2026-07-03", "region": "US", "is_business_day": false }

GET /v1/is-business-day?date=2026-07-03&region=GB
{ "date": "2026-07-03", "region": "GB", "is_business_day": true }

Business-Day API FAQs

Each endpoint returns JSON data that indicates business day status, calculated dates, or the number of working days. For example, the "Is Business Day" endpoint returns whether a specific date is a working day, while the "Add Business Days" endpoint provides the resulting date after adding or subtracting business days.

Key fields in the response include "date" (the input date), "region" (the specified region), "is_business_day" (boolean for business day status), "result" (calculated date), and "business_days" (count of working days between two dates).

Parameters include "date" (required), "region" (required), "subdiv" (optional for subdivisions), "weekend" (optional for custom weekends), "days" (required for adding/subtracting days), and "extra_holidays" (optional for custom blackout dates).

The response data is structured in a JSON format with key-value pairs. Each endpoint's response contains relevant fields based on the request, such as "start," "end," and "result" for date calculations, allowing users to easily parse and utilize the information.

The data is sourced from official holiday calendars for over 100 countries and their subdivisions. The API maintains current holiday information to ensure accuracy, allowing users to rely on it for precise business day calculations.

Typical use cases include logistics and delivery date estimation, financial settlement scheduling, SLA tracking, payroll processing, and appointment scheduling, where accurate business day calculations are crucial for operations.

Users can customize requests by specifying parameters such as "subdiv" for regional subdivisions, "weekend" for non-standard weekends, and "extra_holidays" for custom closures, tailoring the calculations to their specific needs.

Users can utilize the returned data by interpreting the "is_business_day" field to determine scheduling feasibility, using "result" for planning future dates, and leveraging "business_days" for understanding timelines between events or deadlines.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs