Close the confirmation window early
POST
/api/storefront/{brandId}/transactions/{transactionId}/confirmation-window/confirmSecret keySend an sk_live_ key. Server side only.300 requests a minute
The confirmation window replaced escrow in v3.0 and is a STATUS, not a custody arrangement. It records whether a buyer confirmed or disputed. It holds nothing, because there is nothing in Cresva's custody to hold.
Parameters
brandIdstring · pathrequiredThe storefront's brand id. There is no public endpoint that maps a domain to a brand id; ask the merchant for their storefront URL, the id is in it.transactionIdstring · pathrequiredThe transaction id.Request
bash
BRAND_ID=cmqmr1f6j0003la04nu93f4k4
curl -X POST "https://cresva.ai/api/storefront/$BRAND_ID/transactions/{transactionId}/confirmation-window/confirm" \
-H "Authorization: Bearer $CRESVA_SECRET_KEY"Response
No captured response. This operation needs a key. A captured response would mean either printing a real merchant's credential or printing a redacted command nobody can run.
The response schema below is the contract. It comes from the same document the router is checked against, so it is what the endpoint returns even though nobody has printed one here.
Response codes
200The window state.object401The key does not match any active key.erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.403The key is valid but belongs to a different brand than the one in the path. Keys are scoped to one brand and do not travel.erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.404No such brand.erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.429Over the rate limit.erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.503The rate limiter could not be reached, so the request was refused rather than served unmetered. Deliberately not a 429: the caller has done nothing wrong and the fault is ours.erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.Generated from the storefront OpenAPI document at growthagents 269d7898b, sha256 047fe4d301258100. Nothing on this page was typed by hand.