Developer Guides
API Documentation Changelog
Track changes to ScreenVeritAI API documentation, public routes and integration guides. Find the current contract, release notes and migration targets.
Updated
This changelog records changes to the public integration documentation. Use the current OpenAPI contract and endpoint reference when implementing or upgrading a client. Documentation route changes do not change backend endpoint paths or existing API keys.
What this workflow covers
- 11 October 2026 — Consolidated the commercial API introduction and technical integration page under /en/sanctions-screening-api. Old /api-integration and /developer-api links redirect to the same-language hub; the crypto-address-check fragment is retained.
- 11 October 2026 — Published dedicated quickstart and reference pages at /en/developers/quickstart and /en/developers/reference, alongside the existing product-specific guides.
- 11 October 2026 — Published a static public OpenAPI schema at /openapi.json, with a documentation link to the new reference. Interactive v1 documentation remains at /api/v1/docs.
- 11 October 2026 — Consolidated the English PEP integration guide into /en/developers/pep-screening-api, retaining guidance on authentication, polling, batch reconciliation and reviewer evidence.
- Integration compatibility — Existing /api/v1/search, /api/v1/batch and /api/v1/crypto-address/checks contracts are not changed by this documentation migration. Keep existing request paths and review the reference for product-specific execution and billing.
Authoritative references
Questions
Frequently asked questions
Do I need to change my API request URLs for the new documentation hub?
No. The new public documentation URLs do not move the backend /api/v1 endpoints. Update bookmarks and links to the public hub where useful.
Start screening in minutes.
Choose a plan and start screening today.