Calendar Business Day Calculator API

Use the Calendar Business Day Calculator API to retrieve business-day counts, weekend definitions, holiday dates and geographic references as structured JSON from Calendar. Supply country in the query; optionally select date range and category to set the requested scope. Use these results to check working-day intervals or calculate a target date under the selected calendar rules. The detail page includes parameter definitions, paired request and response examples, and usage pricing for this operation.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Country: ISO code or English name. See /calendar/v1/holiday-countries.
Optional parameters (10)
Start date (YYYY-MM-DD; default the first day of this month, or today with `days`).
End date (YYYY-MM-DD; default the last day of start_date's month).
Instead of end_date: business days to add (negative to subtract), up to 1000.
State, province or region code (e.g. `TX`, `BY`, `ENG`) to add its own holidays to the national ones.
Holiday category: `public` (default) or the country's others, e.g. `bank`, `government`, `optional`, `school`, `unofficial`; comma-separated or `all`.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. CSV and NDJSON exports are not supported; omit output or send json.
With output=csv|ndjson: the top-level list to turn into rows (e.g. `reviews`), or `.` for the whole object as one row.

Sample response

{
  "attribution": "Holidays: the open-source holidays project (github.com/vacanza/holidays, MIT)",
  "business_days": 19,
  "cached": false,
  "calendar_days": 30,
  "country_code": "US",
  "credits_used": 1,
  "end_date": "2026-11-30",
  "holidays": [
    {
      "date": "2026-11-11",
      "day_of_week": "Wednesday",
      "holidays": [
        "Veterans Day"
      ],
      "on_weekend": false
    },
    {
      "date": "2026-11-26",
      "day_of_week": "Thursday",
      "holidays": [
        "Thanksgiving Day"
      ],
      "on_weekend": false
    }
  ],
  "holidays_on_business_days": 2,
  "start_date": "2026-11-01",
  "subdivision": null,
  "weekend": [
    "Saturday",
    "Sunday"
  ],
  "weekend_days": 9
}

Response result

Response structure

Inferred from examples
  • attributionstring
  • business_daysinteger
  • cachedboolean
  • calendar_daysinteger
  • country_codestring
  • credits_usedinteger
  • end_datestring
  • holidaysobject[]
    • datestring
    • day_of_weekstring
    • holidaysstring[]
    • on_weekendboolean
  • holidays_on_business_daysinteger
  • start_datestring
  • subdivisionnull
  • weekendstring[]
  • weekend_daysinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Calendar Business Day Calculator API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.