Skip to API documentation
veripoint
Developer documentationAPI v2 + MCP
Request developer access
GETTING STARTED

Authenticate from your server.

Use the Token scheme on every outbound API request.

HTTP headers
Authorization: Token YOUR_API_KEY
Content-Type: application/json
Accept: application/json

Credentials and access

Obtain an API key from your provider account or account manager. Each product can require its own entitlement. An authenticated request may still be denied for an unavailable product or an exhausted allowance.

The examples use GDB_API_KEY. Store it on your server; never put it into browser code, public repositories or query strings. This documentation does not collect API keys.

Choose the right headers

Send JSON bodies with Content-Type: application/json. The AI Financial Research API additionally expects Accept: text/event-stream. GET requests use path and query parameters, not a JSON request body.

Company identifiers and locations

Use the id returned by company search for {id} paths. Keep registration numbers as strings. KYB search accepts ISO country codes, supported country-state codes or KYB nomenclature IDs.

Location lookups
GET /nomenclatures/kyb/countries
GET /nomenclatures/kyb/country/{country_code_iso2}/regions

The regions endpoint is documented for US, CA and CN. Officer search uses nomenclature IDs in company_countries; shareholder search uses ISO codes in location_countries.

Official reference