Count the working days and public holidays in any month.
Working Days counts the working days and non-working days for any country and month. Pass a two-letter country code and month number to get total counts, working date lists, and non-working days marked with holiday names.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"workingDaysCount": 21,
"nonWorkingDaysCount": 10,
"workingDays": [
"2023-10-02",
"2023-10-03",
"2023-10-04",
"2023-10-05",
"2023-10-06",
"2023-10-10",
"2023-10-11",
"2023-10-12",
"2023-10-13",
"2023-10-16",
"2023-10-17",
"2023-10-18",
"2023-10-19",
"2023-10-20",
"2023-10-23",
"2023-10-24",
"2023-10-25",
"2023-10-26",
"2023-10-27",
"2023-10-30",
"2023-10-31"
],
"nonWorkingDays": [
{
"date": "2023-10-01",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-07",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-08",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-09",
"reasons": [
"public holiday"
],
"holiday_name": "Columbus Day"
},
{
"date": "2023-10-14",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-15",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-21",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-22",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-28",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-29",
"reasons": [
"weekend"
],
"holiday_name": null
}
]
}
}
About the Working Days API
Pass a two-letter country code and a month number. The API returns totals for working and non-working days plus a list of working dates formatted as YYYY-MM-DD. Each non-working day specifies reasons such as weekends or public holidays, with holiday names included when applicable. Paid plans can set a custom year.
What people use it for
- Monthly Payroll Proration
- Payroll engines prorate mid-month employee salaries by dividing base pay by the exact working day count for that territory.
- Project Deadline Forecasting
- To forecast delivery deadlines accurately, task management software skips weekends and recognized national holidays across regional teams.
- Retainer Invoice Calculations
- When billing client retainer hours monthly, invoicing software checks total available business days to adjust expected service levels.
- Leave Balance Deductions
- Determine how many days to deduct from employee leave balances by matching vacation requests against official non-working dates.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Working Days
Same data, same APIVerve account, same credit balance — one key works on all of them.
How far does the Starter plan go for working day lookups?
Can I query working days for past or future years on the Free plan?
Does the response break down why a day is considered non-working?
How do I specify which country's working calendar to use?
What does the holiday name field return on normal weekends?
Can I use this data in commercial payroll or scheduling tools?
Request parameters — GET /v1/workingdays
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
countryRequired | string | US | The 2-letter country code you want to get the number of working days for length 2-2 |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
monthOptional | integer | 10 | The month you want to get the number of working days for range 1-12 |
yearOptionalPremium | integer | 2026 | The year you want to get the number of working days for default 2026 · range 2000-2050 |
curl "https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2023" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/workingdays
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"workingDaysCount": 21,
"nonWorkingDaysCount": 10,
"workingDays": [
"2023-10-02",
"2023-10-03",
"2023-10-04",
"2023-10-05",
"2023-10-06",
"2023-10-10",
"2023-10-11",
"2023-10-12",
"2023-10-13",
"2023-10-16",
"2023-10-17",
"2023-10-18",
"2023-10-19",
"2023-10-20",
"2023-10-23",
"2023-10-24",
"2023-10-25",
"2023-10-26",
"2023-10-27",
"2023-10-30",
"2023-10-31"
],
"nonWorkingDays": [
{
"date": "2023-10-01",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-07",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-08",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-09",
"reasons": [
"public holiday"
],
"holiday_name": "Columbus Day"
},
{
"date": "2023-10-14",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-15",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-21",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-22",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-28",
"reasons": [
"weekend"
],
"holiday_name": null
},
{
"date": "2023-10-29",
"reasons": [
"weekend"
],
"holiday_name": null
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
workingDaysCount | number | 21 | Total number of working days in the specified month |
nonWorkingDaysCount | number | 10 | Total number of non-working days in the month |
workingDays | array | [2023-10-02, ...] | Array of dates that are working days (YYYY-MM-DD format) |
nonWorkingDays | array[10] | Array of non-working day objects with dates and reasons | |
date | string | "2023-10-01" | Date of the non-working day in YYYY-MM-DD format |
reasons | array | [weekend] | Array of reasons why day is non-working (weekend, public holiday) |
holiday_name | object | null | Name of holiday if applicable, null for weekends |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Working Days calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/workingdays
No SDK to install — this is a plain HTTPS call to /v1/workingdays with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/workingdays" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/workingdays
Install the Node.js SDK, then call the Working Days API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/workingdaysconst res = await fetch("https://api.apiverve.com/v1/workingdays", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/workingdays
No SDK to install — this is a plain HTTPS call to /v1/workingdays with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/workingdays",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/workingdays
Install the C# / .NET SDK, then call the Working Days API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.WorkingDaysusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/workingdays");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/workingdays
No SDK to install — this is a plain HTTPS call to /v1/workingdays with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/workingdays", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/workingdays
No SDK to install — this is a plain HTTPS call to /v1/workingdays with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/workingdays");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/workingdays
No SDK to install — this is a plain HTTPS call to /v1/workingdays with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/workingdays")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Working Days form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Working Days API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Working Days API.