NOSIBLE
DeveloperAPI reference
Get API key

Find entities

Find the canonical entity or security identifier before retrieving its event timeline.

GET/api/resolve

Related NOSIBLE resources

research & data

Explore the NOSIBLE World interface, inspect the World data dictionary, and browse the classification ontologies used by World.

Authorizations

Bearer
Authorizationstringheader

Required Bearer API key. Programmatic access to the World API needs a key; browsing nosible.world in a browser does not.

Example: Bearer nos_sk_...

Parameters

query & path
qstringrequiredquery

Entity, company, ticker, or identifier to resolve.

Example: nvidia

typesstringquery

Comma-separated entity types or TICKER.

Example: ORG,TICKER

limitintegerquery

Maximum number of candidates. Defaults to 10, maximum 50.

Example: 3

min_eventsintegerquery

Drop candidates with fewer than this many indexed events. Useful for avoiding one-off name collisions.

Example: 25

How to use this endpoint

guidance

Resolve first, retrieve second. The returned canonical spelling and identifier are the safe inputs for the entity and ticker routes; guessing a display name can produce a 404 even when the entity exists. For a security master, keep the identifiers block rather than trying to normalize symbols yourself.

Response body

application/json

These are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.

schemastring

Stable resolver contract identifier.

Example: nosible_world_resolve_v1

qstring

The original lookup query.

Example: nvidia

countinteger

Number of candidates returned.

Example: 2

resultsobject[]

Ranked entity and ticker candidates. Candidate fields vary by kind; use the selected candidate's name or ticker, filter, or events_url in the next request.

Example: [{ kind, type?, ticker?, name, match, score, total_events, first_date, last_date, identifiers?, events_url, filter }]

results[].kindstring

Candidate family: entity or ticker.

Example: ticker

results[].typestring

NER type present on entity candidates.

Example: ORG

results[].tickerstring

Canonical security symbol present on ticker candidates.

Example: NVDA

results[].namestring

Canonical entity or issuer display name.

Example: NVIDIA Corporation

results[].matchstring

Match quality, such as exact or fuzzy.

Example: exact

results[].scorenumber

Resolver ranking score.

Example: 0.998

results[].total_eventsinteger

Indexed event count for the candidate.

Example: 14901

results[].first_datedate

Earliest indexed event date for the candidate when available.

Example: 2015-01-03

results[].last_datedate

Latest indexed event date for the candidate when available.

Example: 2026-07-20

results[].identifiersobject

Alternate security identifiers when the candidate is a ticker.

Example: { "isin": "US67066G1040", "figi": "BBG000BBJQV0", "lei": "549300S4KLFTLO7GSQ80", "wiki_qid": "Q182477" }

results[].events_urlstring

Canonical follow-up URL for the selected candidate.

Example: /world/v1/tickers/NVDA/events

results[].filterobject

Ready-to-use filter expression for POST /api/search.

Example: { "ticker": { "eq": "NVDA" } }

as_ofobject

Index build and archive cutoff used for the lookup.

Example: { "index_build": "...", "archive_cutoff": "2026-07-20" }

took_msnumber

Resolver duration in milliseconds.

Example: 3

Responses and errors

HTTP
200Request succeeded. The response body is shown in the panel on the right.
400invalid_requestThe date, filter, cursor, identifier, or request combination is invalid.
403access_deniedThe requested archive date is outside the caller's World tier.
404not_foundThe requested date, entity, ticker, or event does not exist in the accessible index.
410cursor_expiredThe cursor was minted against a replaced index build. Restart pagination from the first page.
429rate_limitedThe request exceeded the endpoint or account rate limit. Respect Retry-After when supplied.
501backend_not_configuredThe World backend is not configured for this deployment.
502backend_errorThe BFF could not obtain a valid response from the World backend.
504backend_timeoutThe World backend or an upstream data source timed out.
404unknown_entity_or_tickerNo entity or ticker candidate matched the query within the resolver's accessible universe.