|API RANK| by Escape.tech

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

Back to the list Request ranking update

GENERAL INFORMATION

<h1>Authentication</h1> <p>The client must send their assigned PayJustNow Merchant Terminal ID in the <code>X-PayJustNow-Merchant-Terminal-ID</code> request header value. <p>Please use the value <i>1</i> to Authorize the example requests in this document.</p> <h3>Signing</h3> <p>In additional to the above, every <code class="prettyprint">POST</code> or <code class="prettyprint">PATCH</code> request needs to be signed by the client with a <code>X-Signature</code> header value.</p> <p>The <code>X-Signature</code> value is the SHA256 encryption of the request payload with all whitespaces including tabs, newlines, etc. stripped out and signed with the PayJustNow Merchant API Key provided.</p> <p>The PayJustNow Merchant Terminal ID is linked to a Merchant Account, the API Key is stored at the Merchant Account level. Therefore there is a single API key for all terminals linked under an account. <p>Every example signed request in this document will contain the X-Signature for its payload.</p>

...

Contact

  • Name: developer@payjustnow.com

SECURITY 5/5

The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.

  • OWASP: We didn't find any OWASP vulnerability.

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 145 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!

Last scanned: 5/4/2023