---
title: "Re-run decisioning after a change"
method: POST
path: "/v1/customers/{customerId}/reevaluate"
tags: ["Onboarding"]
---

# Re-run decisioning after a change

`POST /v1/customers/{customerId}/reevaluate`

## Request

- Base URL: `https://api.sandbox.alfredpay.io`
- URL: `https://api.sandbox.alfredpay.io/v1/customers/{customerId}/reevaluate`
- Auth: one of:
  - HTTP bearer
  - API key in header `api-key` and API key in header `api-secret`

Use this after corrected data, a new document or an archetype change. It re-runs the decision on what the customer now looks like.

This is the call for material changes, not a second `/verifications`.

## Headers

- `Idempotency-Key` string, uuid, required

## Response `202`

Accepted

- Verification
  - `id` string
  - `submissionId` string
  - `type` 'INDIVIDUAL' | 'BUSINESS'
  - `status` 'SUBMITTED' | 'IN_REVIEW' | 'APPROVED' | 'REJECTED' | 'RFI'
  - `createdAt` string, date-time
  - `updatedAt` string, date-time

## Other responses

- `409`: `idempotency_conflict`, or the resource is in a state that forbids this call.

## Changes

- **2026-11-03** `20fef4fd2ab3`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/alfredpay/apis/alfred-penny-api-client-documentation/changes/v1/customers/:customerId/reevaluate/post.md)

---

[API](https://skmtc.dev/alfredpay/apis/alfred-penny-api-client-documentation.md) - [All operations](https://skmtc.dev/alfredpay/apis/alfred-penny-api-client-documentation/llms.txt) - [OpenAPI document](https://skmtc.dev/alfredpay/apis/alfred-penny-api-client-documentation/revisions/20fef4fd2ab3?raw)