How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Cognism Entitlement API

Read which fields your organisation is licensed for.

Cognism Entitlement API is one of 6 APIs that Cognism publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Entitlement. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a getting-started guide, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2026-08-13.

Requests are made against a single base URL, https://app.cognism.com.

2 operations 2 paths 3 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-08-13
Base URL
https://app.cognism.com
Authentication
HTTP Bearer, API Key
Contact
Terms of Service
Resource Areas
1

Authentication & Security 2

Cognism Entitlement API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the query as api_key (apiKeyQuery). By default, every request must be authenticated.

  • bearerAuth — API token issued in the Cognism app under Settings Tokens and API. Sent as Authorization: Bearer . Tokens have a time-to-live of 6 months.
  • apiKeyQuery — Alternative to the Authorization header. Cognism documents it but recommends the header instead, as the query string is less secure.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Entitlement 2

Read which fields your organisation is licensed for.

GET
/api/search/entitlement/contactEntitlementSubscription
Get contact entitlement details
getContactEntitlement → 200400401404429
GET
/api/search/entitlement/accountEntitlementSubscription
Get account entitlement details
getAccountEntitlement → 200400401404429

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are AccountEntitlement (1 property), ContactEntitlement (1 property). Each schema is shown below with its type and property counts.

ContactEntitlement
object
Map of contact field name to whether the organisation is entitled to it.
1 property
AccountEntitlement
object
Map of account field name to whether the organisation is entitled to it.
1 property
Error
array
Cognism returns errors as an array of error objects.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cognism-entitlement-api-openapi.yml Raw ↑

Other APIs Cognism publishes across the network.

Cognism Compliance API
Cognism Enrich API
Cognism Filter API
Cognism Redeem API
Cognism Search API
Where this information came from

This is an independent, third-party profile of Cognism Entitlement API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.