Add a staff member to the bank

POST 
/v1/bank-staff

Creates a staff member for the calling bank and enqueues identity provisioning. The member is returned in the READY state and transitions to ACTIVE once the identity provider accepts it (see the state machine in the resource state field). Scope rules enforced on the submitted scopes:

• The caller may only grant scopes it already holds itself.

• connector:staff:read / connector:staff:write (staff-administration scopes) may be granted only to a member that also holds the bank-admin role.

• connector:staff:write requires connector:staff:read. Requires the connector:staff:write scope.

Request

Responses

201

Staff member created and queued for identity provisioning.

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.

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.