SteveSteve

Approve a submission in review

Approves a submission in review after all fraud matches are resolved. Returns `409` when verification checks did not pass; a reviewer must approve with a reason. This applies when checks are failed, inconclusive, unavailable, stale, or have not run despite an enabled verification stage (including checks skipped because fraud blocked processing). Resolving fraud matches does not clear this verification gate. A reviewer can run checks in Steve and approve after a current pass, or approve with an audited reason. This endpoint does not accept an override reason.

POST/api/v1/submissions/{submissionId}/approve

Authorization

AuthorizationRequiredBearer <token>

Steve API key, usually scoped to a company. Legacy keys and keys created by platform administrators may be unscoped; company-scoped endpoints reject unscoped keys with 403 Forbidden. Format: Authorization: Bearer aok_...

In: header

Path Parameters

submissionIdRequiredstring

Steve submission identifier.

Header Parameters

X-Request-Idstring

Optional caller-supplied request identifier. Maximum length is 128 characters.

Maximum length: 128
curl -X POST "https://api.meetsteve.io/api/v1/submissions/<string>/approve" \
  -H "X-Request-Id: <string>" \
  -H "Authorization: Bearer <token>"

Submission approved

{
  "submissionId": "string",
  "workflow": {
    "slug": "string",
    "version": 0
  },
  "submissionStatus": "created"
}