|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
FeedAMP Order API (ranked 3213 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/0PgxxBCigUkmn3Sw_8rQm_feedamp_order_api_json.jsonGENERAL INFORMATION
<h2>FeedAMP Process</h2> <ul> <li> FeedAMP frequently imports new orders from a Seller's marketplace accounts for new orders. A Seller can fetch their orders using this FeedAMP Rest API. </li> <li> Seller then confirms order receipt to FeedAMP for each order. </li> <li> After fully shipping and/or cancelling all items, Seller will update the fulfillment information in for the order in FeedAMP. FeedAMP will then forward this information to that order's marketplace account. </li> <li> After fulfillment, a Seller may issue a refund to an order marketplace, by posting a refund to it on FeedAMP. </li> </ul>
<h2>Authentication</h2> <h5>FeedAMP Always enforces IP Whitelisting. The request must come from a white listed ip.</h5> <ul> <li>FeedAMP uses <a target='_blank' href='https://en.wikipedia.org/wiki/Basic_access_authentication'>HTTP Basic Authentication</a> to generate an auth token.</li> <li>The token is used along with a client id in every request until the token expires.</li> <li>When t
...
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 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 495 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 3.0.1 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!