What authentication does the Workday Absence Management API use?

The API uses OAuth 2.0 with an implicit grant flow. Each request requires a valid access token obtained from the tenant-specific authorization hostname. Through Jentic, OAuth tokens are managed in your Jentic One instance so agents never handle raw credentials directly.

Can I submit time-off requests through the Workday Absence Management API?

Yes. The POST /workers/{ID}/requestTimeOff endpoint accepts a time-off request with the absence type, date range, and optional comments. Before submitting, call GET /workers/{ID}/validTimeOffDates to confirm the dates are available and GET /workers/{ID}/eligibleAbsenceTypes to verify the worker qualifies for the selected leave type.

What are the rate limits for the Workday Absence Management API?

Workday enforces tenant-level rate limits that vary by subscription tier, typically allowing 30-60 requests per minute per integration. The API returns HTTP 429 with a Retry-After header when limits are exceeded. Jentic handles automatic retry with exponential backoff for agent-initiated calls.

How do I retrieve a worker's time-off balance through Jentic?

Search Jentic for 'check worker time off balance', load the schema for GET /balances/{ID} or GET /workers/{ID}/timeOffDetails, and execute the call with the worker's Workday ID. The response includes accrued hours, used hours, and remaining balance per absence plan. Install with pip install jentic and authenticate through Jentic One, the self-hosted execution layer.

Does the API support querying multiple workers' absence data at once?

Yes. The GET /workers endpoint returns a paginated list of all workers with absence data. The GET /balances endpoint similarly returns balances across all workers. Both support query parameters for filtering by specific criteria, enabling bulk reporting and dashboard integrations.

Can I limit what my agent is allowed to do with the Workday Absence Management API?

Yes. Because Jentic One is self-hosted, your own rules decide which operations and credentials the agent may use. Workday puts the worker and balance IDs in the URL path, such as /workers/{ID}/timeOffDetails, so you can pin the agent to read-only operations like GET /balances or GET /workers/{ID}/leavesOfAbsence for a specific worker. Write operations such as POST /workers/{ID}/requestTimeOff stay out of reach unless you explicitly allow them.