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

NIBSS Easypay Service (ranked 2985 of 5138)

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

GENERAL INFORMATION

Introduction

The NIBSS Easypay service is a RESTful service that allows financial intermediaries to perform online real-time transactions.
This service consists of 4 methods namely:

  • Balance Enquiry (BE): this is used to retrieve the balance of the target account number provided
  • Name Enquiry (NE): this is used to confirm the name on the account number provided.
  • Fund Transfer (FT): this is used to transfer funds by debiting an originator account to credit a beneficiary account.
  • Transaction Status Query (TSQ): this is used to confirm the status of a Fund transfer credit transaction

Onboarding

To get started with the NIBSS Easypay service API, you need to be profiled on the NIBSS Developer portal.
You have to fill in some basic information for identification purposes. This information is collected in the REQUEST CREDENTIALS FORM. T

...

Contact

  • Name: NIBSS Technical Implementation Support
  • Name: technicalimplementation@nibss-plc.com.ng

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: 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 491 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