Working Days API

OnlineCredit Usage:1 per callRefreshed 1 month ago

avg: 246ms|p50: 233ms|p75: 255ms|p90: 281ms|p99: 335ms

Overview

To use Working Days, you need an API key. You can get one by creating a free account and visiting your dashboard.

GET Endpoint

URL

https://api.apiverve.com/v1/workingdays

Example

How to call the Working Days API in different programming languages.

cURL Request

curl -X GET \
  "https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026" \
  -H "X-API-Key: your_api_key_here"

JavaScript (Fetch API)

const response = await fetch('https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026', {
  method: 'GET',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
});

const data = await response.json();
console.log(data);

Python (Requests)

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

response = requests.get('https://api.apiverve.com/v1/workingdays?country=US&month=10&year=2026', headers=headers)

data = response.json()
print(data)

Go (net/http)

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")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

Example Response

{
  "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
      }
    ]
  }
}

Authentication

The Working Days API requires authentication via API key. Include your API key in the request header:

Required Header

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Working Days API directly in your browser with live requests and responses.

Try Working Days APIView details and test in the API marketplace

Parameters

The following parameters are available for the Working Days API:

Some Working Days parameters marked with Premium are available exclusively on paid plans.View pricing

Get Working Days

Parameter	Type	Required	Description	Default	Example
`country`	string	`required`	The 2-letter country code you want to get the number of working days for Length: `2 - 2 chars`	-	`US`
`month`	integer	`optional`	The month you want to get the number of working days for Range: `1 - 12`	-	`10`
`year`Premium	integer	`optional`	The year you want to get the number of working days for Range: `2000 - 2050`	`2026`	`2026`

Response

The Working Days API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response

200 OK

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <workingDaysCount>21</workingDaysCount>
    <nonWorkingDaysCount>10</nonWorkingDaysCount>
    <workingDays>
      <workingDay>2023-10-02</workingDay>
      <workingDay>2023-10-03</workingDay>
      <workingDay>2023-10-04</workingDay>
      <workingDay>2023-10-05</workingDay>
      <workingDay>2023-10-06</workingDay>
      <workingDay>2023-10-10</workingDay>
      <workingDay>2023-10-11</workingDay>
      <workingDay>2023-10-12</workingDay>
      <workingDay>2023-10-13</workingDay>
      <workingDay>2023-10-16</workingDay>
      <workingDay>2023-10-17</workingDay>
      <workingDay>2023-10-18</workingDay>
      <workingDay>2023-10-19</workingDay>
      <workingDay>2023-10-20</workingDay>
      <workingDay>2023-10-23</workingDay>
      <workingDay>2023-10-24</workingDay>
      <workingDay>2023-10-25</workingDay>
      <workingDay>2023-10-26</workingDay>
      <workingDay>2023-10-27</workingDay>
      <workingDay>2023-10-30</workingDay>
      <workingDay>2023-10-31</workingDay>
    </workingDays>
    <nonWorkingDays>
      <nonWorkingDay>
        <date>2023-10-01</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-07</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-08</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-09</date>
        <reasons>
          <reason>public holiday</reason>
        </reasons>
        <holiday_name>Columbus Day</holiday_name>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-14</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-15</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-21</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-22</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-28</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
      <nonWorkingDay>
        <date>2023-10-29</date>
        <reasons>
          <reason>weekend</reason>
        </reasons>
        <holiday_name xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
      </nonWorkingDay>
    </nonWorkingDays>
  </data>
</response>

YAML Response

200 OK

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

CSV Response

200 OK

key	value
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}]

View in Marketplace

Response Structure

All API responses follow a consistent structure with the following fields:

Field	Type	Description	Example
`status`	string	Indicates whether the request was successful ("ok") or failed ("error")	`ok`
`error`	string \| null	Contains error message if status is "error", otherwise null	`null`
`data`	object \| null	Contains the API response data if successful, otherwise null	`{...}`

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Field	Type	Sample Value	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)
[ ] Array items:	array[10]	`Array of objects`	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

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Working Days through GraphQL to combine it with other API calls in a single request. Query only the working days data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Working Days in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint

POST https://api.apiverve.com/v1/graphql

GraphQL Query Example

query {
  workingdays(
    input: {
      country: "US"
      month: 10
      year: 2026
    }
  ) {
    workingDaysCount
    nonWorkingDaysCount
    workingDays
    nonWorkingDays
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

Try in GraphQL Explorer GraphQL Documentation

CORS Support

The Working Days API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Working Days requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Working Days API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Working Days

Official Working Days packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

Working Days works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

How do I get an API key for Working Days?

Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Working Days and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.

How many credits does Working Days cost?

Each successful Working Days API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful working days lookups.

Can I use Working Days in production?

The free plan is for testing and development only. For production use of Working Days, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Working Days from a browser?

Yes! The Working Days API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.

What happens if I exceed my Working Days credit limit?

When you reach your monthly credit limit, Working Days API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Browse All APIs

Explore our complete catalog of APIs

Authentication Guide

Learn about API keys and security

Rate Limits

Understand usage limits and best practices

Was this page helpful?

Working Days API

Overview

GET Endpoint

Example

Authentication

Interactive API Playground

Parameters

Get Working Days

Response

Other Response Formats

Response Structure

Response Data Fields

Headers

GraphQL AccessALPHA

CORS Support

Rate Limiting

Error Codes

SDKs for Working Days

No-Code Integrations

Frequently Asked Questions

People who used this also used...

World Holidays

Liturgical Calendar

Date Calculator

What's Next?

Browse All APIs

Authentication Guide

Rate Limits