|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Subscribe API (ranked 3200 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/zVbNFd_w4jJLqV_Sf571L_subscribe_api_json.jsonGENERAL INFORMATION
Overview
The REST API for Subscribe provides predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients
Subscribe OpenAPI YAML Reference
See the Subscribe OpenAPIs YAML file located in the Developer Hub section of the Knowledge Center.
Environment
Subscribe provides two distinct environments for testing and production:
The Staging Environment
The Staging environment allows you to test your application against the code currently running in Production: https://api.staging.us-west.vindicia.com
The Production Environment
The Production environment is for real-world use for actual billing and subscription activity.
https://api.vindicia.com
*Note: The examples in this API referenc
...
Contact
- Name: support@vindicia.com
License
- Name: Vindicia
- See License
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: A05: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 629 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!