The state of public APIs| Submit an API

|API RANK| by Escape.tech

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

Back to the list Request ranking update

Banking API (ranked 2539 of 5138)

https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/_Sh4d_JjOEIXWtLJrqf7f_banking_api_json.json

GENERAL INFORMATION

REST API to handle Banking and Cash Management to support straight through
processing and automated payments via integrations to other banking systems.

Authentication

The API conforms to the OAuth2 standard for security and uses Microsoft's Azure Active Directory (AAD)
as a trusted identity provider and security token service. So to acquire an access token you will need to first authenticate with Microsoft's AAD.

Try it

To use the "Try it out" features from within this documentation site, you will need to acquire and send a valid bearer token under Authorization request header.

  • Retrieve an access_token by following the instructions outlined within the Client credentials grant section below.

Client credentials grant

For authentication from a service or deamon not running in the context of a logged in user should use [client credentials grant flow](https://too

...

Contact

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 501 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: 3/1/2023