Skip to main content
POST
Preview pod staffing reconciliation
Compares a pod staffing assignment (podAssignmentId) with the pod’s current roster, without changing anything: the current memberships, the project’s and the pod assignment’s staffing rows, the workers, whether the roster changed, and the drift to reconcile. A pod assignment of another project is 404 ending (STAFFING_ASSIGNMENT_NOT_FOUND). A pod managed by a customer organization, or by a unit under one, answers 404 exactly as a missing pod. This is a read carried in a POST body: it changes nothing and takes no Idempotency-Key. Needs workforce:manage at the platform scope (a grant that covers only some org units receives 403) and projects:read at the project’s home: a project that is missing, has no home, or that you cannot read answers 404. Because the answer is a staffing read, the credential’s scopes must include workforce:read and projects:read as well as workforce:manage (otherwise 403 naming the missing one, and nothing changes). A refusal is 400, 404, 409 or 413 and its message ends with the Console’s code in parentheses.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

projectId
string
required

The project's ID (id from GET /api/v2/projects/list).

Minimum string length: 1
podAssignmentId
string
required

The pod staffing assignment's ID (from GET /api/v2/projects/getPodStaffing).

Minimum string length: 1

Response

Success

data
object
required
meta
object
required