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

Refinitiv Authentication API

OAuth 2.0 token management for obtaining and refreshing access tokens required by all other API endpoints.

Refinitiv Authentication API is one of 45 APIs that Refinitiv publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.refinitiv.com, https://selectapi.datascope.lseg.com/RestApi/v1.

2 operations 2 paths 1 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.refinitiv.com
Authentication
HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Refinitiv Authentication API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (tokenAuth).

  • bearerAuth — OAuth 2.0 Bearer token obtained from the /auth/oauth2/v1/token endpoint. Access tokens are valid for five minutes.
  • tokenAuth — Session token obtained from the Authentication/RequestToken endpoint. Include as Token followed by the token value.

Paths & Operations 2

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

Authentication 2

OAuth 2.0 token management for obtaining and refreshing access tokens required by all other API endpoints.

POST
/auth/oauth2/v1/token
Request Access Token
getToken body → 200400401
POST
/Authentication/RequestToken
Request Authentication Token
requestToken body → 200400401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is TokenResponse (5 properties). Each schema is shown below with its type and property counts.

TokenResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

refinitiv-authentication-api-openapi.yml Raw ↑

Other APIs Refinitiv publishes across the network.

Refinitiv Data Library for Python
Refinitiv Data Library for .NET
Refinitiv Data Platform Libraries
Eikon Data API
Refinitiv Real-Time WebSocket API
Refinitiv Real-Time SDK - Java
Refinitiv Real-Time SDK - C/C++
Refinitiv News API
Refinitiv ESG API
LSEG DataScope Select - SOAP API
LSEG Tick History REST API
Datastream Web Service API
Where this information came from

This is an independent, third-party profile of Refinitiv Authentication 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.