Update Entity CIP Status

Use PATCH on /cipStatus to override an entity's CIP (Customer Identification Program) status. This endpoint is an override, not a setter: it only changes a status that your program's onboarding flow has already decided.


⚠️ Warning: Directly editing an entity's CIP status will override the CIP status set by the program. Only call this endpoint for an entity that already has a decided CIP status.


Preconditions

  • The entity must have a decided CIP status of pass or fail. If cip.status is absent or pend, the request will return 400 because there is nothing to override yet.
  • When setting the status to pass, every non-archived beneficial owner with cipRequired set to true must already have a CIP status of pass, otherwise the request is rejected.

📘 Note: An entity's CIP status is produced by completing the business's KYB onboarding flow. Use this endpoint only to override an already-decided status, not to force an initial decision.


Error Codes

The codes below are not listed in evaluation order.

Error CodeHTTP StatusDescription
CIP_NOT_YET_DETERMINED400No CIP decision has been reached yet (the CIP status is absent or pend), so there is nothing to override.
BENEFICIAL_OWNERS_CIP_STATUS_NOT_PASS400One or more required beneficial owners do not have a CIP status of pass, so the entity cannot be set to pass.
USER_NOTHING_TO_MODIFY400The requested CIP status already matches the entity's current status; there is nothing to update.
ENTITY_NOT_FOUND404No active entity with this id exists for your program.
Path Params
string
required

Pass in the Spidr entity ID

Body Params

PATCH /v1/entity/:id/cipStatus Request body

string
enum
required

The CIP status, if enrolled.

Allowed:
string
required

The reason for manually updating the CIP status

Responses

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json