Skip to main content
This page highlights notable integration-facing changes. Use it to understand behavior changes that might affect your webhook consumers, status handling, or dashboard workflows.

​
2026-08-18

​
Added company verification webhook events

Company verification now uses dedicated event names:
  • company_verification.submitted
  • company_verification.liveness_completed
  • company_verification.under_review
  • company_verification.successful
  • company_verification.failed

​
Expanded company verification webhook payloads

Company verification webhook payloads now include a normalized companyProfile block and a review block so downstream systems can consume:
  • business registration details
  • contact details
  • authorised representative details
  • officers and ownership details
  • provisioning-readiness and review metadata

​
Clarified company verification lifecycle

Company verification documentation now reflects the current lifecycle:
  • not started
  • started
  • submitted
  • under review
  • successful
  • failed

​
Clarified test vs live company decision behavior

  • Test company verifications can be moved through review and terminal states from the customer dashboard for testing
  • Live company verifications keep final terminal decisions under Helium ID internal control

​
Clarified company verification ID behavior

Company verification documentation now distinguishes:
  • public company verification ID returned as verificationId
  • internal company verification ID sent as companyVerificationId
  • hosted-flow processId
  • public externalId

​
Clarified create-endpoint success responses

The current verification creation endpoints return HTTP 200 success responses with a JSON body that also includes code: 200.

​
Notes for integrators

  • Treat webhook payloads as extensible. New optional fields and new event types may be added over time.
  • Handle unknown webhook event names gracefully.
  • Prefer storing raw webhook payloads for replay and audit purposes.
For compatibility expectations, see Backwards Compatible Changes.