For the complete documentation index, see llms.txt.

Add Business Days to Date API

time-date 1 credit / call v2026-04-22

Add or subtract business days from a date, skipping weekends under a configurable workweek pattern.

One POST adds Add Business Days to Date to your app, site, workflow, or agent — formula, validation, edge cases, and docs already handled.

prefer a UI? Open the Add Business Days to Date on miniwebtool.com →

Start free — get a key → 1,000 credits · no card · 30 seconds

Endpoint

POST · 1cr
POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run

Request body

Field Type Req.
start_date
ISO date YYYY-MM-DD
 str ✓
business_days int —
direction
add | subtract
 str —
workweek
mon_fri | mon_sat | sun_thu | mon_sun
 str —
start_adjust
keep | next | prev
 str —

Cost & access

  • 1 credit per successful call — failed calls refund.
  • Starts on: Free.
  • Max payload: 65536 bytes.
  • Privacy mode: hash_only
  • Available on: free, starter, pro, business, scale

Response envelope

{
  "request_id": "01K...",
  "tool": "add-business-days-to-date",
  "tool_version": "2026-04-22",
  "credits_used": 1,
  "result": { ... }
}

Try it

Stored only in this browser tab. Playground test key is prefilled and only works on this page. Get a live key →
ISO date YYYY-MM-DD
add | subtract
mon_fri | mon_sat | sun_thu | mon_sun
keep | next | prev

Get your own key

1,000 free calls/mo · no card · key arrives by email

One verification click, then your key + a ready-to-run request. No card, no spam.

Code examples

curl -X POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run \
  -H 'Authorization: Bearer mwt_live_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"start_date":"2026-07-20","business_days":10,"direction":"add","workweek":"mon_fri"}'
import requests

resp = requests.post(
    'https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run',
    headers={'Authorization': 'Bearer mwt_live_YOUR_KEY'},
    json={'start_date': '2026-07-20', 'business_days': 10, 'direction': 'add', 'workweek': 'mon_fri'},
)
resp.raise_for_status()
data = resp.json()
print(data)
const resp = await fetch(
  'https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run',
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer mwt_live_YOUR_KEY',
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({"start_date":"2026-07-20","business_days":10,"direction":"add","workweek":"mon_fri"}),
  }
);
const data = await resp.json();
console.log(data);
<?php
$ch = curl_init('https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer mwt_live_YOUR_KEY',
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode([
    'start_date' => '2026-07-20',
    'business_days' => 10,
    'direction' => 'add',
    'workweek' => 'mon_fri'
]),
]);
$resp = curl_exec($ch);
curl_close($ch);
print_r(json_decode($resp, true));
require 'net/http'
require 'json'
require 'uri'

uri = URI('https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = (uri.scheme == 'https')

req = Net::HTTP::Post.new(uri)
req['Authorization'] = 'Bearer mwt_live_YOUR_KEY'
req['Content-Type'] = 'application/json'
req.body = {
  'start_date' => '2026-07-20',
  'business_days' => 10,
  'direction' => 'add',
  'workweek' => 'mon_fri'
}.to_json

resp = http.request(req)
puts JSON.parse(resp.body).inspect
package main

import (
  "bytes"
  "encoding/json"
  "fmt"
  "io"
  "net/http"
)

func main() {
  body, _ := json.Marshal(map[string]interface{}{
    "start_date": "2026-07-20",
    "business_days": 10,
    "direction": "add",
    "workweek": "mon_fri",
  })
  req, _ := http.NewRequest("POST", "https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run", bytes.NewReader(body))
  req.Header.Set("Authorization", "Bearer mwt_live_YOUR_KEY")
  req.Header.Set("Content-Type", "application/json")

  resp, err := http.DefaultClient.Do(req)
  if err != nil { panic(err) }
  defer resp.Body.Close()
  out, _ := io.ReadAll(resp.Body)
  fmt.Println(string(out))
}
import java.net.URI;
import java.net.http.*;

var client = HttpClient.newHttpClient();
var req = HttpRequest.newBuilder()
    .uri(URI.create("https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run"))
    .header("Authorization", "Bearer mwt_live_YOUR_KEY")
    .header("Content-Type", "application/json")
    .POST(HttpRequest.BodyPublishers.ofString("{\"start_date\":\"2026-07-20\",\"business_days\":10,\"direction\":\"add\",\"workweek\":\"mon_fri\"}"))
    .build();

var resp = client.send(req, HttpResponse.BodyHandlers.ofString());
System.out.println(resp.body());
agents let your coding agent do it

Copy this into Claude Code, Cursor, Codex, Aider or Cline. It carries the endpoint, the full schema, a sample response, and the credit rules — so the agent wires add-business-days-to-date up correctly without draining your key.

Free to iterate: the prompt points the agent at POST /v1/tools/add-business-days-to-date/dry-run, which validates the request and returns the response shape for 0 credits. Only the final confirmation call is billed (1 credit).
Stable URL for this prompt: /tools/add-business-days-to-date/prompt.md (?variant=cursor / ?variant=mcp).
Paste into Claude Code, or save as CLAUDE.md context.
Integrate the MiniWebtool Add Business Days to Date API into this project.

## Your task

1. Read the reference below.
2. Ask me where this belongs in the codebase if it is not obvious.
3. Write the integration in the language and style of the surrounding code:
   a small typed client function, errors handled, key read from the
   environment (never hard-coded, never committed).
4. Verify with `/dry-run` first, then exactly one live call.
5. Show me the diff and the live result.

## Credit budget — follow these exactly

This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.

1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
   payload for real and returns a sample result with the exact response shape.
   Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
   dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
   against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
   `application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
   stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
   tool is deterministic, so the same input always returns the same output.

## The API

**Add Business Days to Date** — Add or subtract business days from a date, skipping weekends under a configurable workweek pattern.

- Live endpoint: `POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run` — costs 1 credit
- Dry run: `POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/dry-run` — costs 0 credits, same auth and validation
- Auth: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
- Content type: `application/json`
- Tool version: `2026-04-22` (output shape is stable within a major version)
- Full machine-readable spec: `https://api.miniwebtool.com/v1/openapi.json`

### Request body

| field | type | required | notes |
|---|---|---|---|
| `start_date` | str | yes | ISO date YYYY-MM-DD |
| `business_days` | int | no | (default `10`) |
| `direction` | str | no | one of: add, subtract — add \| subtract (default `add`) |
| `workweek` | str | no | one of: mon_fri, mon_sat, sun_thu, mon_sun — mon_fri \| mon_sat \| sun_thu \| mon_sun (default `mon_fri`) |
| `start_adjust` | str | no | one of: keep, next, prev — keep \| next \| prev (default `keep`) |

Example request body:

```json
{
  "start_date": "2026-07-20",
  "business_days": 10,
  "direction": "add",
  "workweek": "mon_fri"
}
```

### Response envelope

```json
{
  "request_id": "req_01H…",
  "tool": "add-business-days-to-date",
  "tool_version": "2026-04-22",
  "credits_used": 1,
  "result": {
    "start_date": "2026-07-20",
    "start_date_weekday": "Monday",
    "start_date_was_business_day": true,
    "adjusted_start_date": null,
    "business_days": 10,
    "direction": "add",
    "workweek": "mon_fri",
    "result_date": "2026-08-03",
    "result_weekday": "Monday",
    "calendar_days_elapsed": 14,
    "weekend_days_skipped": 4
  }
}
```

`result` holds the tool output. Errors come back as
`application/problem+json` with `type`, `title`, `status`, and `detail`.

### Getting a key

If `MINIWEBTOOL_API_KEY` is not already in the environment, stop and ask me for
one — do not sign up, scrape, or guess a key. Free keys: https://api.miniwebtool.com/dashboard/
Paste into Codex, Aider, Cline, or any coding agent.
Integrate the MiniWebtool Add Business Days to Date API into this project.

## Your task

1. Read the reference below.
2. Ask me where this belongs in the codebase if it is not obvious.
3. Write the integration in the language and style of the surrounding code:
   a small typed client function, errors handled, key read from the
   environment (never hard-coded, never committed).
4. Verify with `/dry-run` first, then exactly one live call.
5. Show me the diff and the live result.

## Credit budget — follow these exactly

This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.

1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
   payload for real and returns a sample result with the exact response shape.
   Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
   dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
   against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
   `application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
   stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
   tool is deterministic, so the same input always returns the same output.

## The API

**Add Business Days to Date** — Add or subtract business days from a date, skipping weekends under a configurable workweek pattern.

- Live endpoint: `POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run` — costs 1 credit
- Dry run: `POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/dry-run` — costs 0 credits, same auth and validation
- Auth: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
- Content type: `application/json`
- Tool version: `2026-04-22` (output shape is stable within a major version)
- Full machine-readable spec: `https://api.miniwebtool.com/v1/openapi.json`

### Request body

| field | type | required | notes |
|---|---|---|---|
| `start_date` | str | yes | ISO date YYYY-MM-DD |
| `business_days` | int | no | (default `10`) |
| `direction` | str | no | one of: add, subtract — add \| subtract (default `add`) |
| `workweek` | str | no | one of: mon_fri, mon_sat, sun_thu, mon_sun — mon_fri \| mon_sat \| sun_thu \| mon_sun (default `mon_fri`) |
| `start_adjust` | str | no | one of: keep, next, prev — keep \| next \| prev (default `keep`) |

Example request body:

```json
{
  "start_date": "2026-07-20",
  "business_days": 10,
  "direction": "add",
  "workweek": "mon_fri"
}
```

### Response envelope

```json
{
  "request_id": "req_01H…",
  "tool": "add-business-days-to-date",
  "tool_version": "2026-04-22",
  "credits_used": 1,
  "result": {
    "start_date": "2026-07-20",
    "start_date_weekday": "Monday",
    "start_date_was_business_day": true,
    "adjusted_start_date": null,
    "business_days": 10,
    "direction": "add",
    "workweek": "mon_fri",
    "result_date": "2026-08-03",
    "result_weekday": "Monday",
    "calendar_days_elapsed": 14,
    "weekend_days_skipped": 4
  }
}
```

`result` holds the tool output. Errors come back as
`application/problem+json` with `type`, `title`, `status`, and `detail`.

### Getting a key

If `MINIWEBTOOL_API_KEY` is not already in the environment, stop and ask me for
one — do not sign up, scrape, or guess a key. Free keys: https://api.miniwebtool.com/dashboard/
Save as .cursor/rules/miniwebtool-add-business-days-to-date.mdc
---
description: MiniWebtool Add Business Days to Date API — usage and credit budget
globs:
alwaysApply: false
---

# MiniWebtool Add Business Days to Date API

## The API

**Add Business Days to Date** — Add or subtract business days from a date, skipping weekends under a configurable workweek pattern.

- Live endpoint: `POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run` — costs 1 credit
- Dry run: `POST https://api.miniwebtool.com/v1/tools/add-business-days-to-date/dry-run` — costs 0 credits, same auth and validation
- Auth: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
- Content type: `application/json`
- Tool version: `2026-04-22` (output shape is stable within a major version)
- Full machine-readable spec: `https://api.miniwebtool.com/v1/openapi.json`

### Request body

| field | type | required | notes |
|---|---|---|---|
| `start_date` | str | yes | ISO date YYYY-MM-DD |
| `business_days` | int | no | (default `10`) |
| `direction` | str | no | one of: add, subtract — add \| subtract (default `add`) |
| `workweek` | str | no | one of: mon_fri, mon_sat, sun_thu, mon_sun — mon_fri \| mon_sat \| sun_thu \| mon_sun (default `mon_fri`) |
| `start_adjust` | str | no | one of: keep, next, prev — keep \| next \| prev (default `keep`) |

Example request body:

```json
{
  "start_date": "2026-07-20",
  "business_days": 10,
  "direction": "add",
  "workweek": "mon_fri"
}
```

### Response envelope

```json
{
  "request_id": "req_01H…",
  "tool": "add-business-days-to-date",
  "tool_version": "2026-04-22",
  "credits_used": 1,
  "result": {
    "start_date": "2026-07-20",
    "start_date_weekday": "Monday",
    "start_date_was_business_day": true,
    "adjusted_start_date": null,
    "business_days": 10,
    "direction": "add",
    "workweek": "mon_fri",
    "result_date": "2026-08-03",
    "result_weekday": "Monday",
    "calendar_days_elapsed": 14,
    "weekend_days_skipped": 4
  }
}
```

`result` holds the tool output. Errors come back as
`application/problem+json` with `type`, `title`, `status`, and `detail`.

### Getting a key

If `MINIWEBTOOL_API_KEY` is not already in the environment, stop and ask me for
one — do not sign up, scrape, or guess a key. Free keys: https://api.miniwebtool.com/dashboard/

## Credit budget — follow these exactly

This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.

1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
   payload for real and returns a sample result with the exact response shape.
   Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
   dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
   against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
   `application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
   stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
   tool is deterministic, so the same input always returns the same output.
Skip the HTTP client — connect the agent directly.
Add the MiniWebtool MCP server to this project, then use the
`add-business-days-to-date` tool from it.

Server URL: https://api.miniwebtool.com/v1/mcp
Transport: HTTP (Streamable HTTP / JSON-RPC 2.0)
Auth header: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`

Claude Code:

```bash
claude mcp add --transport http miniwebtool https://api.miniwebtool.com/v1/mcp \
  --header "Authorization: Bearer $MINIWEBTOOL_API_KEY"
```

Or add it to the MCP config file your client uses:

```json
{
  "mcpServers": {
    "miniwebtool": {
      "type": "http",
      "url": "https://api.miniwebtool.com/v1/mcp",
      "headers": { "Authorization": "Bearer ${MINIWEBTOOL_API_KEY}" }
    }
  }
}
```

Once connected, `tools/list` exposes `add-business-days-to-date` with its JSON Schema, so you can
call it directly instead of writing an HTTP client.

## Credit budget — follow these exactly

This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.

1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
   payload for real and returns a sample result with the exact response shape.
   Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
   dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
   against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
   `application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
   stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
   tool is deterministic, so the same input always returns the same output.
how-to call add-business-days-to-date
  1. Get an API key
    Get an API key. Sign up free for a bearer token. 1,000 credits/month, no card.
  2. Assemble the JSON body
    Required fields: start_date, . See the Request body table above for the full schema.
  3. POST to https://api.miniwebtool.com/v1/tools/add-business-days-to-date/run
    Headers: Authorization: Bearer <key> and Content-Type: application/json. Copy-paste snippets in 7 languages are under Code examples.
  4. Parse the response
    Envelope: {request_id, tool, tool_version, credits_used, result}. The typed output lives in result.
faq frequently asked
What does the Add Business Days to Date API do?+

Add or subtract business days from a date, skipping weekends under a configurable workweek pattern. Use it to add this utility without rebuilding formulas, validation, examples, and documentation.

How much does one call to Add Business Days to Date cost?+

1 credit per successful call. Failed calls (validation errors, 5xx) don't bill.

What parameters does the Add Business Days to Date API require?+

Required fields: start_date. Full schema at /v1/openapi.json.

Is the Add Business Days to Date API deterministic?+

Yes — same input, same output, forever. Tool version 2026-04-22; output shape is stable within a major version.

Can an AI agent call the Add Business Days to Date API?+

Yes. Connect to https://api.miniwebtool.com/v1/mcp over the Model Context Protocol. The agent discovers `add-business-days-to-date` with its JSON Schema automatically, so the model can plan while MiniWebtool handles the exact tool result.

What format does the API return?+

JSON with a stable envelope: `{request_id, tool, tool_version, credits_used, result}`. Errors are RFC 7807 `application/problem+json`.

mcp use from an AI agent

Every endpoint on this site is also exposed via the Model Context Protocol at https://api.miniwebtool.com/v1/mcp. Claude, Cursor, and any MCP-capable agent can discover this tool (add-business-days-to-date) and its JSON Schema automatically — no client codegen. 

# List tools the agent can call
curl -s https://api.miniwebtool.com/v1/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
 | jq '.result.tools[] | select(.name=="add-business-days-to-date")'
see-also related time-date tools
Days in Month
Number of days in a given month/year with leap-year detection and calendar boun…
Age Calculator
Exact age in years/months/days plus total days, next-birthday countdown, day bo…
Time Zone Converter
Convert a local date/time between IANA time zones with DST-aware offsets, to on…
Military Time Converter
Convert between 12-hour, 24-hour, and military time, including the spoken milit…