SKILL.md
Sumsub — Create POA Preset
Builds a POA preset JSON payload from a compact spec, POSTs it to the Sumsub API, and reports the resulting preset id so it can be attached to one or more levels via level.requiredIdDocs.docSets[].poaStepSettingsId.
Prerequisite — level must have a PROOF_OF_RESIDENCE step. A POA preset has no effect unless it is attached to a
PROOF_OF_RESIDENCE(orPROOF_OF_RESIDENCE2/3/4) docset in at least one level. If the user hasn't created (or described) a level that includes a POA step, surface this before building the preset — there is no point creating it in isolation.
Endpoints
| Method | Path | When |
|---|---|---|
POST |
/resources/api/agent/poaStepSettings |
Create a new preset. Body MUST NOT include id — server assigns it. |
PATCH |
/resources/api/agent/poaStepSettings |
Update an existing preset. Body MUST include id (the field, not in the URL). |
GET |
/resources/api/agent/poaStepSettings/{id} |
Read one preset back — used to verify what landed and to resolve name from a known id. |
All three require permission manageClientSettings. Body shape is the
POA preset schema — client-settable
fields only (clientId, createdAt, createdBy, modifiedAt, audit
trail are server-managed and echoed back on the response).