Update a pending staff member

PUT 
/v1/onboarding-cases/:case_id/staff-members/:staff_id

Replaces the email, role labels and scopes of a staff member. All three are required; the same rules apply as on create (see POST .../staff-members).

Required scope: connector:staff:write.

Preconditions: the member is in state READY, the case is in AWAITING_BANK_ADMIN, BANK_CONFIGURING or NEEDS_CHANGES, and the case has no activation operation yet. Otherwise the call returns 409 (detail: staff member or onboarding case is no longer editable).

data.id must equal the staff_id path parameter (otherwise 400 RESOURCE_ID_MISMATCH). No Idempotency-Key is used; repeating the request has the same effect.

Request

Responses

200

Staff member updated.

400

The request is malformed: invalid JSON syntax, an invalid path or query parameter, a missing required header such as Idempotency-Key, or a single field that fails its own format rule. Fix the request before retrying; retrying it unchanged fails again.

401

The bearer token is missing, malformed, expired, signed by an unknown key, or was not issued by the platform IAM for the Lyriq Connector. Obtain a new token and retry. See the Authentication section.

403

The token is valid but may not perform this request: it lacks the required scope, has no bank membership, needs an x-dan-bank-id header to choose between several memberships, names a bank in x-dan-bank-id it has no membership for, or the caller's bank is suspended or terminated. A new token with the same configuration fails the same way. See the Authentication section.

404

The resource does not exist, or it belongs to another bank. The Lyriq Connector does not distinguish the two cases, so resources of other banks are never disclosed.

409

The member or the case is no longer editable, or the new email is already used on the case.

422

The request is well-formed JSON but cannot be processed: the body does not match the expected shape (a missing or unknown member, a wrong type, or a wrong data.type), or it breaks a business or cross-field rule. Correct the request before retrying.

503

The request could not be served right now. Either the network is not fully operational (OUTBOUND_HALTED or READ_ONLY: mutations are refused while read endpoints keep working; OPERATIONAL_STATE_UNKNOWN: the state could not be determined), or a platform dependency is temporarily unavailable. No Retry-After header is sent; retry later with backoff. When retrying a mutation, reuse the same Idempotency-Key and body.