Developers
Integrate once, switch modules on later
Register customers over a signed, idempotent API, subscribe to lifecycle webhooks, and let each tenant run only the checks they are licensed for.
Developers
Built API-first, not API-eventually
The dashboard your analysts use is the same API your engineers call. Register customers, subscribe to lifecycle webhooks and reconcile state without screen-scraping anything.
- Signed webhooks with at-least-once delivery and replay-safe payloads
- Idempotent registration keyed on your own external customer ID
- Oomero ID: onboard a subject once, reuse the verified record everywhere
Register a company from your CRM
curl -X POST https://api.oomero.com/api/v1/crm/registrations \ -H "x-api-key: $OOMERO_API_KEY" \ -H "content-type: application/json" \ -d '{ "sourceSystem": "salesforce", "externalCustomerId": "ACME-88213", "onboardingType": "company", "company": { "name": "Acme Holdings Ltd", "registrationNumber": "09876543", "jurisdiction": "GB" }, "modules": ["kyb", "aml_screening", "ubo_discovery"] }'201 Createdapplication/json
{ "oomeroId": "GB0000188213", "status": "awaiting_verification", "checks": { "registry": "queued", "vat": "queued", "screening": "queued" }, "webhookTopics": [ "onboarding.status_changed", "screening.match_found" ]}One layer over the registries your regulator expects you to check
- Companies HouseUK registry & officers
- HMRCUK VAT verification
- VIESEU VAT validation
- GLEIFLegal Entity Identifiers
- DigiLockerIndia document vault
- PANIndia tax identity
See Oomero with your own customers
We will take your team through a real onboarding, for a person and a company, using your own risk policy, and show you exactly what is recorded.