> ## Documentation Index
> Fetch the complete documentation index at: https://lava.so/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Workday

> Workday REST API access for reading workers and worker data from a connected Workday tenant.

Workday REST API access for reading workers and worker data from a connected Workday tenant. Use when an agent needs worker records, employment data, or the current user's identity from Workday. Routes through Pipedream Connect; the user authorizes a Workday integration system user once and Lava holds no Workday token. Note: Workday's REST surface covers a subset of HR data and each Workday tenant lives on its own host, which Pipedream resolves automatically.

3 example endpoints available through Lava's AI Gateway. See the [Workday API docs](https://community.workday.com/sites/default/files/file-hosting/restapi/index.html) for full documentation.

<Warning>This provider requires your own credentials — connect your API key or OAuth account before use.</Warning>

<Info>This is a **catch-all provider** — any valid URL under `https://workday.com` is supported. Workday REST API. Workday is a per-tenant app: each customer's REST base (host + /ccx/api/\<service>/\<version>/\<tenant>) lives inside the connected account, and Pipedream resolves it. Send RELATIVE paths only; the literal host workday.com is routing-only. Common reads: /workers (list), /workers/\{id} (one worker; \{id} is a Workday WID, not an email), /workers/me (the authenticated worker, useful as an identity probe). Pagination is limit + offset (limit default 20, max 100; offset zero-based). Caveat: the connection's stored base usually targets the common/v1 surface, so domain-specific reads (staffing, absenceManagement) may require their own /\<service>/\<version>/ path segment and the matching OAuth scope; those are not guaranteed to resolve under the default base. Auth is brokered by Pipedream, do not send an Authorization header. This provider is read-only: only GET requests are supported. The endpoints below are curated examples.</Info>

## Endpoints

### List workers (employees and contingent workers) in the connected tenant. Paginate with limit (max 100) and offset.

**GET** `https://workday.com/workers?limit=20&offset=0` — Free

<Tabs>
  <Tab title="SDK">
    ```typescript theme={null}
    const data = await lava.gateway('https://workday.com/workers?limit=20&offset=0', { method: 'GET' });
    ```
  </Tab>

  <Tab title="cURL">
    ```bash theme={null}
    curl "https://api.lava.so/v1/forward?u=https%3A%2F%2Fworkday.com%2Fworkers%3Flimit%3D20%26offset%3D0" \
      -H "Authorization: Bearer $LAVA_SECRET_KEY"
    ```
  </Tab>
</Tabs>

### Get one worker by Workday ID (WID): personal data, employment, business title, and primary supervisory organization.

**GET** `https://workday.com/workers/{id}` — Free

<Tabs>
  <Tab title="SDK">
    ```typescript theme={null}
    const data = await lava.gateway('https://workday.com/workers/{id}', { method: 'GET' });
    ```
  </Tab>

  <Tab title="cURL">
    ```bash theme={null}
    curl "https://api.lava.so/v1/forward?u=https%3A%2F%2Fworkday.com%2Fworkers%2F%7Bid%7D" \
      -H "Authorization: Bearer $LAVA_SECRET_KEY"
    ```
  </Tab>
</Tabs>

### Get the currently authenticated worker. Use as an identity probe to confirm which tenant and user the connection is bound to (requires the Workday-owned scope on the client).

**GET** `https://workday.com/workers/me` — Free

<Tabs>
  <Tab title="SDK">
    ```typescript theme={null}
    const data = await lava.gateway('https://workday.com/workers/me', { method: 'GET' });
    ```
  </Tab>

  <Tab title="cURL">
    ```bash theme={null}
    curl "https://api.lava.so/v1/forward?u=https%3A%2F%2Fworkday.com%2Fworkers%2Fme" \
      -H "Authorization: Bearer $LAVA_SECRET_KEY"
    ```
  </Tab>
</Tabs>

## Next Steps

<CardGroup cols={2}>
  <Card title="All Providers" icon="grid" href="/gateway/supported-providers">
    Browse all supported AI providers
  </Card>

  <Card title="Forward Proxy" icon="route" href="/gateway/forward-proxy">
    Learn how to construct proxy URLs and authenticate requests
  </Card>
</CardGroup>