|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Jumpseller API (ranked 462 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Jumpseller_API_fa5c1c4e_8671_4c3d_9a23_6f32498bc4b8_json.jsonGENERAL INFORMATION
Endpoint Structure
All URLs are in the format:
https://api.jumpseller.com/v1/path.json?login=XXXXXX&authtoken=storetoken
The path is prefixed by the API version and the URL takes as parameters the login (your store specific API login) and your authentication token.
<br/><br/>
Version
The current version of the API is v1.
If we change the API in backward-incompatible ways, we'll increase the version number and maintain stable support for the old urls.
<br/><br/>
Authentication
The API uses a token-based authentication with a combination of a login key and an auth token. Both parameters can be found on the left sidebar of the Account section, accessed from the main menu of your Admin Panel. The auth token of the user can be reset on the same page.
The auth token is a 32 characters string.
If you are developing a Jumpseller App, the authentication should be done using [OAuth-2](/support/o
...
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 4/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 109 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 2/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!