ForHosting KIT · Developer Utilities

Ship-by date calculator

A ship-by date calculator answers the fulfillment question every storefront and warehouse planner faces: if the customer must receive the order by a fixed promised delivery day and the carrier needs a known number of working days in transit, what is the latest calendar day you can still hand the package to the carrier?

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Enter a strict ISO delivery date and a non-negative integer transit workday count—for example delivery on Monday the twenty-seventh with five working days of transit—and the tool walks backward on the Gregorian calendar while skipping every Saturday and Sunday, then returns the ship-by ISO date, weekday names, ISO weekday numbers, and the calendar span between ship and delivery. Public holidays are intentionally out of scope so regional calendars do not silently rewrite a global SLA. The path is pure deterministic arithmetic—no network, no wall-clock Date, no random seed—so the free browser runner and the prepaid API return the same JSON every time you call it.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

How do I use this capability?

Complete the fields above and run it on this page. The form highlights anything that needs attention.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/date/ship-by-date

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/date/ship-by-date \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"delivery_date":"2026-07-27","transit_days":5}'

const res = await fetch("https://api.kit.forhosting.com/date/ship-by-date", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "delivery_date": "2026-07-27",
    "transit_days": 5
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/date/ship-by-date",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "delivery_date": "2026-07-27",
    "transit_days": 5
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/ship-by-date", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"delivery_date":"2026-07-27","transit_days":5}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"delivery_date":"2026-07-27","transit_days":5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/ship-by-date", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "delivery_date": "2026-07-27",
  "transit_days": 5
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "date.ship_by_date",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Read the full KIT documentation →