The state of public APIs| Submit an API

|API RANK| by Escape.tech

Benchmark and ranking of 5138+ public APIs by Escape.tech

Back to the list Request ranking update

TradingView REST API Specification for Brokers (ranked 4155 of 5138)

https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/postman_com_devrel_workspace_tradingview_sample_public_workspace_json.json

GENERAL INFORMATION

Overview

This API is to be implemented by the Brokers in order to connect their backend systems to TradingView, that acts as a frontend.

Check the info page for more info and use the contact form there if you have any questions.

Types of requests

There are two types of requests — client and server.
Client requests are executed at the browser. Server requests are initiated from the TradingView servers.
If your integration does not imply brokerage data stream connection to the TradingView website -
then there won't be any server requests.

Clients requests

From the browser TradingView requests the info (list of orders and positions, balance info, etc.) from the broker’s server.
The requests are sent periodically and the intervals can be set by using the /config endpoint.
After that, TradingView compares the new data with the previous answer and calculates the diffe

...

SECURITY 4/5

The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.

  • OWASP issues detected: API7:2023

PERFORMANCE 0/5

The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.

  • The median response time of the API is 5,000 ms .

Get p50 under 220 ms to get a 4/5 score.

RELIABILITY 5/5

The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.

  • Self compliance: response objects matched the declared response types.
  • Server errors: the server did not return any 5xx error.

DESIGN 3/5

The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.

  • Respects OpenAPI 3.0.0 schema specification.
  • Contains comments and summaries.
  • Contains examples.
  • Does not contain duplicated objects.

Popularity 0/5

The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!

Last scanned: 5/4/2023