{
"from": {
"datetime": "2026-01-31T13:00:00+03:00",
"timezone": "Africa/Nairobi",
"utc_offset": "+03:00",
"abbreviation": "GMT+3",
"utc": "2026-01-31T10:00:00Z",
"unix": 1769853600
},
"to": {
"datetime": "2026-03-15T11:30:00+03:00",
"timezone": "Africa/Nairobi",
"utc_offset": "+03:00",
"abbreviation": "GMT+3",
"utc": "2026-03-15T08:30:00Z",
"unix": 1773563400
},
"direction": "forward",
"total": {
"milliseconds": 3709800000,
"seconds": 3709800,
"minutes": 61830,
"hours": 1030.5,
"days": 42.9375,
"weeks": 6.1339
},
"calendar": {
"years": 0,
"months": 1,
"days": 11,
"hours": 22,
"minutes": 30,
"seconds": 0
},
"note": "Le détail calendaire est calculé sur les dates UTC des deux instants."
}
curl --location --request GET 'https://zylalabs.com/api/15137/clearcheck+date+and+timezone+utilities+api/40391/difference+between+two+datetimes' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the ClearCheck Date and Timezone Utilities API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
It returns normalized details for both inputs, including the original datetime, IANA timezone, UTC offset, abbreviation, UTC value, and Unix timestamp. It also provides direction plus total milliseconds, seconds, minutes, hours, days, and weeks, followed by a calendar breakdown.
The `total` fields represent the exact elapsed duration between instants. The `calendar` fields provide years, months, days, hours, minutes, and seconds. The calendar detail is calculated using the UTC dates of the two instants, as indicated by the response note.
Working-day operations support configurable weekends and holidays. Supply the starting date or date range together with the desired working-day rules and holiday dates. This allows schedules to reflect local business calendars rather than assuming only Saturday and Sunday are non-working.
It returns the date reached after adding the requested number of working days according to the supplied weekend and holiday configuration. Use it for deadlines, delivery estimates, payroll dates, or other schedules that must skip non-working days.
It calculates the number of working days between two dates using the configured weekend and holiday rules. The result is useful for measuring business processing time, leave duration, service windows, and other intervals where calendar days are not sufficient.
Conversion uses IANA timezone identifiers, such as `Africa/Nairobi`, and accounts for timezone offset changes, including daylight-saving transitions. Responses can include the converted datetime, UTC offset, abbreviation, UTC representation, and Unix timestamp for reliable cross-region comparisons.
The current-time endpoint provides the present date-time context for a requested IANA zone, including offset-related information. The zone-list endpoint returns supported IANA timezone identifiers, which can be used to validate or populate timezone-selection inputs before conversion requests.
Errors use a consistent JSON structure: `{"error":{"code","message"}}`. Clients should inspect both the machine-readable `code` and human-readable `message`, and validate dates, timezone identifiers, and request parameters before retrying or displaying the result.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund