Document SCREENING_UNAVAILABLE on the 500 error - #1035
ls-bolt[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
✱ Stainless preview builds for gridThis PR will update the cli go kotlin openapi php python ruby typescript Edit this comment to update them. They will appear in their respective SDK's changelogs. ✅ grid-typescript studio · code · diff
✅ grid-openapi studio · code · diff
✅ grid-kotlin studio · code · diff
✅ grid-ruby studio · code · diff
✅ grid-go studio · code · diff
✅ grid-python studio · code · diff
✅ grid-php studio · code · diff
✅ grid-cli studio · code · diff
This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push. |
A request halted because sanction screening could not reach a verdict is a failure on our side, not a finding about the caller, and is safe to retry. It answers 500 rather than the 403 SANCTION_BLOCKED a genuine block still carries.
faee4df to
292f707
Compare
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
2 participants
Summary
Adds
SCREENING_UNAVAILABLEto theError500code enum.When sanction screening cannot reach a verdict — the screening provider is
unreachable or fails to answer — the request is refused without any finding
having been made about the caller. That is a failure on the API side, so it now
answers
500 SCREENING_UNAVAILABLEand is safe to retry.A genuine sanctions block is unchanged: it still answers
403 SANCTION_BLOCKED,which correctly tells the caller that retrying will not help.
Every endpoint affected already declares a
500response carryingError500,so this adds a code to an existing enum rather than a new response shape.
Requested by @AaryamanBhute