---
title: "Resolve a requirement"
method: PUT
path: "/accounts/entities/{id}/requirements/{requirementId}"
tags: ["Onboarding", "Platforms"]
---

# Resolve a requirement

`PUT /accounts/entities/{id}/requirements/{requirementId}`

## Request

- Base URL: `https://{prefix}.api.sandbox.checkout.com`
- URL: `https://{prefix}.api.sandbox.checkout.com/accounts/entities/{id}/requirements/{requirementId}`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `string` scopes: `accounts`
  - API key in header `Authorization`
- TypeScript: <https://skmtc.dev/checkout/apis/checkout-com-api-reference/docs/accounts/entities/:id/requirements/:requirementId/put.ts> (a function with typed inputs; its response is checked against the schema)

Submit a response to resolve a requirement. The shape of `value` is defined by the requirement's `_schema`, returned from `GET /accounts/entities/{id}/requirements/{requirementId}`.

The response is accepted for processing and applied asynchronously. While processing, the requirement is no longer retrievable via the GET endpoints; if validation fails downstream the requirement may reappear.

## Request body

- EntityRequirementUpdateRequest: Request body used to resolve a requirement. The shape of `value` is defined by the requirement's `_schema` (returned from `GET /accounts/entities/{id}/requirements/{requirementId}`).
  - `value` union, required: The response to the requirement. The expected shape depends on the requirement and is defined by the JSON Schema returned in the requirement details response. Common shapes include a file reference (for document uploads), a primitive value, or a structured object.
    - object
    - unknown[]
      - unknown
    - string
    - number
    - boolean

## Response `202`

Response accepted for processing

- EntityRequirementUpdateResponse: Acknowledges that a requirement response has been accepted for processing.
  - `id` string: The unique identifier of the requirement.
  - `status` 'processing': Processing status of the submitted response. While the response is processing, the requirement is no longer retrievable via the GET endpoints; if validation fails downstream the requirement may reappear.
  - `submitted_at` string, date-time: The date and time, in ISO 8601 UTC format, the response was accepted.
  - `_links` object

## Other responses

- `400`: The request body could not be parsed.
- `401`: Unauthorized
- `404`: Requirement not found, or a response has already been submitted for it.
- `422`: The supplied `value` did not validate against the requirement's `_schema`.

---

[API](https://skmtc.dev/checkout/apis/checkout-com-api-reference.md) - [All operations](https://skmtc.dev/checkout/apis/checkout-com-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/checkout/apis/checkout-com-api-reference/revisions/0f1abdb1c3e9?raw)