|API RANK| by Escape.tech

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

Back to the list Request ranking update

GENERAL INFORMATION

Calls are facilitated using Mashery API Services. All endpoints are only accessible over https and are located at https://api.vistana.com (https://api-qa.vistana.com for nonprod).

Mashery is used for endpoint authentication as well as rate limiting (by both queries per second and queries per day).

Base URLs

Production:
https://api.vistana.com/dcm/{version}/{authtype}/{endpoint}
EXAMPLE
https://api.vistana.com/dcm/v1/oauth/properties
QA:
https://api-qa.vistana.com/coh/{version}/{authtype}/{endpoint}
EXAMPLE
https://api-qa.vistana.com/dcm/v1/oauth/properties

Limits

By default api keys are limited to 10 queries per second with a maximum of 25000 requests per day.

Mashery

For more information on specific service details related to login, registration, and account updates. Please refer to the Vistana Mobile API Documentation. There you will find specific details on how to register your devi

...

Contact

  • Name: Michael Waskiewicz
  • Name: michael.waskiewicz@vistana.com

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 3/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 354 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 1/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!

Last scanned: 5/4/2023