---
title: "Workday Staffing APIs: Open Requisitions & Headcount"
description: "How to read open job requisitions, unfilled positions, and supervisory org headcount via Workday Staffing REST, SOAP, and WQL while protecting compensation."
url: https://kiweely.com/guides/workday-staffing-api-job-requisitions-open-positions-managers
---

# Querying Open Job Requisitions and Supervisory Org Headcount via Workday Staffing APIs

Workday exposes supervisory org rosters on staffing v7 and common v1 REST APIs, while open job requisitions and unfilled position seats live in WQL (jobRequisitionsByRole, openPositionsByOrganization) and Recruiting/Staffing SOAP—enforcing manager role boundaries and protecting compensation.

-   **Checked** against Workday on November 15
-   Applies to **Workday Staffing APIs & WQL**
-   5 min read
-   Published November 15
-   By Kiweely

To answer a hiring manager’s live headcount and open-role questions in Workday without over-exposing executive searches or confidential pay bands, combine **`staffing/v7` and `common/v1` REST** (`GET /workers/{ID}/supervisoryOrganizationsManaged`, `GET /supervisoryOrganizations/{ID}/members`) for active team rosters with **Workday Query Language (`POST /wql/v1/data`)** on `jobRequisitionsByRole` and `openPositionsByOrganization` for open requisitions and unfilled position seats.

A common surprise for engineers building manager dashboards is discovering that `recruiting/v4` REST (`GET /jobPostings`) only lists **externally published career-site postings**—missing unposted internal backfills, frozen requisitions, and unfilled **Position Management** chairs that do not yet have a requisition attached. Knowing which Workday API surface owns each piece of the staffing model prevents miscounted headcount.

## Mapping Workday Staffing & Recruiting Surfaces

| Question to Answer | Best API Surface | Resource / Data Source / Operation | Required Scope & Security Domains |
| --- | --- | --- | --- |
|  **Which Supervisory Orgs does this manager lead?** | REST `common/v1` | `GET /workers/{ID}/supervisoryOrganizationsManaged` | Scope: `Organizations and Roles`; Domain: `Reports: Organization`. |
|  **Who is currently active in this Supervisory Org?** | REST `staffing/v7` or `common/v1` | `GET /supervisoryOrganizations/{ID}/members` & `/orgChart` | Scope: `Organizations and Roles` / `Staffing`; Domains: `View: Supervisory Organization`, `Reports: Organization`. |
|  **Which Job Requisitions are open for my team?** | WQL (`wql/v1`) or SOAP `Recruiting` | WQL `jobRequisitionsByRole` / `allJobRequisitions`; SOAP `Get_Job_Requisitions` | Scope: `Recruiting` / `Staffing`; Role-constrained Job Requisition domains. |
|  **Which Position Management seats are unfilled or frozen?** | WQL (`wql/v1`) or SOAP `Staffing` | WQL `openPositionsByOrganization` / `allOpenPositions`; SOAP `Get_Positions` | Scope: `Staffing` / `Jobs & Positions`; Position Management reporting domains. |
|  **Which roles are live on the external career site?** | REST `recruiting/v4` | `GET /jobPostings` | Scope: `Recruiting`; Domain: `Job Postings: External`. |

## Step 1: Resolve Managed Supervisory Organizations and Active Headcount

In Workday, headcount belongs to a **Supervisory Organization** (`Supervisory Organization`), and managers frequently oversee both a top-level org and nested subordinate teams (see [subordinate org security intersection](https://kiweely.com/guides/workday-security-groups-intersection-subordinate-org-visibility)).

Start by querying `GET /common/v1/workers/{ID}/supervisoryOrganizationsManaged` under the signed-in manager’s OAuth credential, then read active filled members via `GET /staffing/v7/supervisoryOrganizations/{org_ID}/members` (or `GET /common/v1/workers/{ID}/directReports` for immediate direct reports under `Self-Service: My Team`). Always check whether your definition of headcount counts **Employees** only or includes **Contingent Workers**, and whether workers currently `(On Leave)` with `Allow Job Overlap for Leave` enabled occupy the same position alongside a temporary backfill.

## Step 2: Query Open Job Requisitions via WQL (`jobRequisitionsByRole`)

To list open, pending-approval, or frozen requisitions—including target hire dates, days open, and recruiting start dates—run a WQL query against `jobRequisitionsByRole`:

sql

```
SELECT
  workdayID,
  referenceID1,
  jobPostingTitle,
  supervisoryOrganization,
  jobProfileHiringRequirement,
  jobRequisitionPrimaryLocation,
  workerTypeHiringRequirement,
  timeTypeHiringRequirement,
  jobRequisitionStatus,
  recruitingStartDate,
  targetHireDate,
  numberOfDaysOpen
FROM jobRequisitionsByRole
WHERE jobRequisitionStatus IN ('Open', 'Frozen')
ORDER BY recruitingStartDate ASC
```

Why prefer `jobRequisitionsByRole` over `allJobRequisitions` for manager self-service?

-   **Constrained Role Filtering:** `jobRequisitionsByRole` scopes rows to requisitions where the signed-in user holds an authorized role (`Manager`, `Recruiting Manager`, `Primary Recruiter`, or `HR Partner`) on that Supervisory Organization.
-   **Confidential Job Requisitions Excluded:** When executive recruiting creates a **Confidential Job Requisition** (for example, replacing an incumbent leader), Workday isolates access strictly to explicitly assigned confidential recruiting roles—preventing subordinate or peer managers from discovering confidential backfills through org-wide queries.
-   **Evergreen vs. Standard Requisitions:** Note that `allJobRequisitions` and `jobRequisitionsByRole` include both standard requisitions and high-volume **Evergreen Requisitions**; inspect linked positions or requisition type fields so high-volume retail evergreen funnels do not double-count approved seats alongside linked child requisitions.
-   **Multi-Org Requisition Display (`tyc1482947881469`):** In Position Management organizations, if a non-confidential Job Requisition spans multiple positions across different Supervisory Organizations, Workday displays a single primary Supervisory Organization based on its multi-position resolution rules—so always reconcile against `openPositionsByOrganization` when auditing exact seat counts per manager.

## Reconciling Headcount Math Across Filled, On-Leave, and Open Seats

Before presenting a headcount summary to a department leader, verify these four reconciliation rules against your tenant’s staffing model:

1.  **Position Management vs. Job Management:** A Supervisory Organization uses either **Position Management** (individual seat IDs with explicit hiring restrictions) or **Job Management** (org-level hiring restrictions without seat IDs). `openPositionsByOrganization` returns position-level rows for Position Management orgs, whereas Job Management orgs track open demand primarily through `jobRequisitionsByRole` and headcount plans (`headcountPlanLines`).
2.  **Job Overlap During Leaves of Absence:** When `Allow Job Overlap for Leave` is active on a Position Management seat, both the employee on parental/medical leave and their temporary backfill occupy the same position—filter active vs. `(On Leave)` status explicitly so budgeted seat counts match Finance numbers.
3.  **Committed Pre-Hires (`futurePositionFill_EffectiveDate`):** Separate truly vacant seats from seats where an offer has been accepted (`Offer` completed, `Hire` effective next month) so managers do not open duplicate requisitions.
4.  **SOAP Alternative (`Get_Job_Requisitions` & `Get_Positions`):** When downstream systems require nested XML structures such as full qualification profiles or position restriction details, invoke `Get_Job_Requisitions` (`Recruiting` SOAP) and `Get_Positions` (`Staffing` SOAP) using the signed-in manager’s OAuth 2.0 Bearer header.

## Step 3: Reconcile Unfilled Positions in Position Management (`openPositionsByOrganization`)

In **Position Management** organizations, an approved seat (`P-00841`) can sit unfilled **before** a manager opens a Job Requisition, or after a requisition closes unfilled. Query `openPositionsByOrganization` (which requires the `organization` parameter) to capture total approved capacity:

sql

```
SELECT
  workdayID,
  positionAndJob_AllStaffingModels,
  supervisoryOrganization,
  jobProfile,
  hiringRestrictions_Location,
  hiringRestrictions_WorkerType,
  scheduledWeeklyHours,
  availabilityDate,
  earliestHireDate,
  hiringFreeze,
  positionCount_Filled,
  positionsUnfilled,
  positionCount_Available,
  futurePositionFill_EffectiveDate
FROM openPositionsByOrganization(
  organization = '7a19d402c8e5100014b28890ab120055'
)
```

Pay close attention to `futurePositionFill_EffectiveDate` and `pre_HiresConsideredForPositionCount`: a position where a candidate has already accepted an offer and has a future **Hire** effective date next Monday is technically unfilled *today*, yet already committed—showing `futurePositionFill_EffectiveDate` stops hiring managers from double-requesting a backfill.

## Protecting Confidential Compensation Boundaries

Even when a manager has full `View: Supervisory Organization` visibility into open positions and job requisitions, compensation fields carry independent domain security:

1.  **Domain Separation inside WQL and SOAP:** On `openPositionsByOrganization`, fields like `defaultBasePaySegment` and `hasDefaultCompensation` are secured separately from `jobProfile` and `availabilityDate`. Under user-delegated OAuth, if a frontline supervisor lacks position/requisition compensation domain permissions, Workday either refuses a `SELECT` containing unauthorized pay columns or returns blank values depending on the field’s security policy.
2.  **Select Only Needed Non-Pay Columns by Default:** Keep default staffing queries scoped to structural fields (`jobPostingTitle`, `jobProfile`, `location`, `targetHireDate`, `jobRequisitionStatus`, `hiringFreeze`), and pair external connectors with **in-memory field-level redaction** if HR partners with broader tenant permissions share screen views during planning meetings.

Organizations tired of exporting weekly Excel headcount trackers can publish a live, one-page **Manager View** using **[Kiweely Leaf](https://kiweely.com/leaf)** (coming next—showing filled headcount, open requisitions, unfilled seats, and who is out this week on live Workday APIs without a Workday Extend license), or let leaders ask headcount and requisition questions directly inside Claude, ChatGPT, and Gemini via **[Kiweely Bridge](https://kiweely.com/bridge)** (coming next, enforcing each manager’s own Workday role boundaries and RAM-level field redaction rules).

## Frequently asked questions

### Why doesn't the Workday recruiting v4 REST API return internal open job requisitions and headcount?

The recruiting v4 REST API exposes external career-site jobPostings, prospects, interviews, and candidate offers—not internal unposted requisitions or position seats. Query WQL jobRequisitionsByRole / allJobRequisitions or Recruiting SOAP Get\_Job\_Requisitions for internal requisition status.

### What is the difference between an unfilled Position and an Open Job Requisition in Workday?

In Position Management supervisory organizations, a Position (P-xxxxx) is an approved headcount seat that may be unfilled with no active recruiting, frozen, or linked to an open Job Requisition (JR-xxxxx). Job Management organizations skip individual seats and recruit directly against Job Requisitions.

### Which WQL data source automatically scopes job requisitions to a hiring manager's role?

Use jobRequisitionsByRole (Primary Business Object: Job Requisition) under user-delegated OAuth. Workday restricts returned rows to requisitions the signed-in user is authorized to view through their Manager, Recruiting Manager, or Recruiter role assignments, excluding confidential executive searches.

### How does Workday prevent peer managers or recruiters from seeing confidential requisition compensation?

Target requisition compensation, replacement worker names, and position defaultBasePaySegment fields sit behind separate domain security policies (such as Job Requisition Compensation and Worker Data: Compensation) rather than general View: Supervisory Organization or Reports: Organization domains.

## Sources checked

-   [Reference: Supervisory Organizations on Job Requisitions](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/job-requisitions/tyc1482947881469.html)
-   [Steps: Set Up Job Requisitions](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/job-requisitions/deb1440609261597.html)
-   [Set Up Supervisory Organizations](https://doc.workday.com/admin-guide/en-us/manage-workday/organizations/dan1370797386252.html)
-   [Setup Considerations: Job Requisitions for Recruiting](https://doc.workday.com/admin-guide/en-us/human-capital-management/recruiting/job-requisitions-for-recruiting/fsn1558961997264.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas Verify Workday security boundaries in Sandbox before rolling out reports, APIs, or external tools by combining four checks: View Security for Securable Item, Security Analysis for Securable Item and Account, Start Proxy UI checks, and user-delegated REST/WQL API readback.](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner)
-   [### Querying the Workday Worker Directory, Supervisory Hierarchy, and Cost Centers with WQL Use Workday Query Language (WQL) against indexedAllWorkers or workersForHCMReporting to query worker business titles, managers, supervisory organizations, locations, and cost centers in a single HTTP request while enforcing the caller’s contextual Workday domain security.](https://kiweely.com/guides/workday-worker-directory-org-chart-search-fields-wql)
-   [### Preventing Accidental Indirect-Report Visibility in Workday Intersection Security Groups Managers and HR Partners see unintended indirect reports in Workday for two reasons: setting component Role-Based Security Groups to Current Organization and All Subordinates (COAS) instead of COO/COUS, or leaving component groups on domain policies alongside an Intersection Security Group.](https://kiweely.com/guides/workday-security-groups-intersection-subordinate-org-visibility)
-   [### Should I use RaaS, WQL or the REST API to extract data from Workday? Use RaaS for a saved report’s output, WQL for a filtered, grouped or paged extract of up to 1 million rows, and REST for small, low-latency reads of one resource. Limits and sources are in the table.](https://kiweely.com/guides/workday-raas-wql-rest)

### More guides on WQL

[All 31 guides](https://kiweely.com/guides#wql)

-   [Finding Unsubmitted Workday Time Blocks and Project Hours with WQL](https://kiweely.com/guides/workday-project-time-tracking-unsubmitted-hours-wql)
-   [Querying Pending Workday My Tasks and Inbox Approvals via API and WQL](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql)
-   [Why fileLength on workerDocuments Returns 52 in WQL for Business Process Attachments](https://kiweely.com/guides/wql-workerdocuments-filelength-returns-52)
-   [Paging with POST /wql/v1/data in a PMD Grid When Queries Exceed URL Limits](https://kiweely.com/guides/wql-post-data-endpoint-grid-pagination-url-limit)
-   [Escaping Single Quotes for Multi-Value IN Clauses and Fixing Double URL-Encoded Unicode in PMD WQL](https://kiweely.com/guides/wql-pmd-single-quote-escaping-double-urlencoded-unicode)
-   [Filtering WQL Queries by Organization Hierarchy and workersByRole Without Throwing Security Errors](https://kiweely.com/guides/wql-organization-hierarchy-filter-workersbyrole)
-   [Why WQL Queries on findCandidates and allWorkers Return Empty Right After a Business Process Step](https://kiweely.com/guides/wql-indexing-delay-findcandidates-bp-status-change)
-   [Fixing WQL Error 804 on GROUP BY and Related Business Object Aggregation Limits](https://kiweely.com/guides/wql-group-by-error-804-rbo-aggregation-limits)

### From the blog on WQL

[All posts](https://kiweely.com/blog)

-   [What happens after ChatGPT writes your WQL query](https://kiweely.com/blog/after-chatgpt-writes-your-wql)
-   [Answering Executive Span-of-Control and Headcount Questions Live from Workday](https://kiweely.com/blog/executive-org-span-of-control-attrition-questions-live-workday)
-   [Build vs. Buy a Workday MCP Server: OAuth 2.1, SOAP, WQL, and Twice-Yearly Releases](https://kiweely.com/blog/build-vs-buy-workday-mcp-server-engineering-cost)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
