|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Threads REST API (ranked 3406 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Threads_REST_API_0133c504_781a_4f62_97ae_81e3fff75572_yaml.yamlGENERAL INFORMATION
Introduction
This API is currently in beta.
Please e-mail engineering@threadsculture.com to receive a client ID and secret to access the API. You must have an active Threads account with a admin user credentials to use this API.
For bug reports and feature requests, please use our github repo issue tracker at: https://github.com/ThreadsCulture/REST-API/issues
OAuth Authentication
API Authentication is done via an OAuth token. To retrieve an oauth token, send an HTTP POST
request to https://YOUR-COMPANY-PORTAL.ourthreads.com/oauth/token
This request should have the following query parameters:
client_id
- Client IDclient_secret
- Client secretgrant_type
- Should always be "password"email
- The e-mail address of the user account the API will function on behalf ofpassword
- The password of the user account the API will function on behalf of
Note that these parameters should be sent in the query string of the request, not as POST data. cURL example:
...
Contact
- Name: engineering@threadsculture.com
SECURITY 3/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: A05:2021, A07:2021
PERFORMANCE 2/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 456 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 2/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 2.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!