|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Facility Codes (ranked 2941 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/RuovA86plL4Cke4nqgjqb_facility_codes_json.jsonGENERAL INFORMATION
A common API to provide the details of a facility used in International trade comprising of the BIC Container Facilities and SMDG Terminal Codes, these codes are managed under the ownership of each organisation independently but provided under a single API to industry. Bureau International des Containers (BIC) are responsible for providing the inland container facilities within a country, or location. SMDG are responsible for providing the terminals that container vessels call at within a country or location. Both codes are an extension of the UN/LOCODE designed to give granularity of facilities contained within the area identified by the UN/LOCODE. Both the BIC Facility Codes and the SMDG Terminal Codes are child codes of the UN/LOCODE, For further information and to request an API key visit the terms of service website for details.
Contact
- Name: BIC API Support
- Name: bic@bic-code.org
- Contact API maintainers
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 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 208 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 1/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!