Overview
Working Days works by analyzing the data provided and returning the number of working days in the given month. It uses various sources to determine the data and returns the number of working days.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
countryRequired | string | The 2-letter country code you want to get the number of working days for length 2–2 |
monthOptional | integer | The month you want to get the number of working days for range 1–12 |
yearOptionalPremium | integer | The year you want to get the number of working days for default 2026 · range 2000–2050 |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Other ways to use Working Days
Set up Working Days on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Calendar: