Response Codes and checkResult
1 day ago by Jason Langkamer-Smith
/start Endpoint Response Code Documentation
/start Endpoint Response Code DocumentationWe've added comprehensive response code documentation for the /start endpoint, covering all expected HTTP status codes with detailed examples.
- 200 OK — Four integration pattern examples (Direct polling, Direct webhook, Capture with SMS, Capture with redirect).
- 400 Bad Request — 11 error examples across request errors and field validation errors, with guidance on resolution.
- 401 Unauthorized — Authentication failure scenarios.
- 404 Not Found — Route errors.
- 500 Internal Server Error — Server-side error handling.
checkResult & processResult Property Updates
checkResult & processResult Property UpdatesWe've updated the API reference to clarify the checkResult and processResult response properties.
checkResultis now documented on the/barcode-onlyand/get-resultsendpoints with defined enum values (0–4).processResultis marked as deprecated — usecheckResultinstead. This is a documentation update only, not a breaking change.- There is no change to the
get-transaction-dataendpoint. It retains the snake_casecheck_resultproperty.
