November 2026: Improved onboarding guide, document IDs and a new documents endpoint

Changed

  • Submission checks can now block submission. For Atlas for Platform sub-accounts, Get submission checks now returns blocking issues while background checks are running, if they fail, while an uploaded document is still being read, and when a check couldn't verify part of the application. Wait for the checks to finish and fix these before submitting. Submitting with them open returns a 422.

Added

  • Get documents to submit. A new endpoint, GET /companies/{companyId}/documentsToSubmit, returns the documents each sub-account needs and the document type ID for each. If you'd rather not hard-code the list of IDs, call it for each sub-account to get both the documents that are required and the IDs. See Get documents to submit.
  • Upload documents without choosing a type. Use the one shared document type ID when you get an upload link, and leave the type out when you attach the document. Verto works out each document's type automatically. See the Uploading documents section in Sub-account onboarding.
  • Onboarding Operations Guide. A new guide that walks you and your clients through the onboarding process operationally: what happens after you apply, identity checks, requests for information, accepting the Terms & Conditions, and who to contact. See the Onboarding Operations Guide.

Improved

  • Sub-account onboarding guide (V3). We've improved the documentation. It now says what to collect and when, then shows how to submit, check and track an application. See Sub-account onboarding.
  • Document Type IDs. We've updated the guide to be more inclusive of the documents an application can need, and clearer about which document ID to use for each. See Document Type IDs.
  • More onboarding fields documented. Add or update onboarding data now lists fields the API accepted but the docs didn't show: website, social media links, business description, incorporation date and company addresses.