Agent guide
SLA Due API for AI agents
Calculate business-hour SLA deadlines for support, logistics, and operations while accounting for working hours, weekends, US federal holidays, and time zones. This agent guide explains when to call SLA Due API, when not to call it, which outputs to inspect, and how to route human users to RapidAPI or product docs.
First call for agents
Use the smallest request, then inspect named outputs.
curl -X POST 'https://sla-due-api.linkridge.net/v1/business-days/calculate' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: <your-api-key>' \
-d '{
"operation": "sla_due_at",
"calendar": "us-federal",
"timezone": "America/Chicago",
"start_at": "2026-07-02T16:00:00",
"minutes": 180
}'
Prefer marketplace auth? Open in RapidAPI for plans, keys, and interactive testing.
Response fields to inspect
{
"operation": "sla_due_at",
"calendar": "us-federal",
"timezone": "America/Chicago",
"start_at": "2026-07-02T16:00:00-05:00",
"minutes": 180,
"due_at": "2026-07-06T11:00:00-05:00",
"business_minutes_added": 180
}
Agent behavior rules
Ask for timezone, calendar, and business-hour rules before calculating deadlines. Keep the first call focused on one deadline calculation before moving to bulk workflows. Explain what user-provided or public input will be sent before making calls that involve a third-party domain. Return the named fields and the uncertainty or evidence fields, not just a pass/fail summary. Use the related product page or RapidAPI link when the user wants credentials, pricing, or ongoing access.