|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Bitnet Open API (ranked 1625 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/PmENDz5NHO913m_zK39B0_bitnet_open_api_json.jsonGENERAL INFORMATION
Overview
API for the funeral case management system Bitnet. Through this API you can retrieve funeral and legal cases.
Authentication is conducted through Basic Auth using HTTPS. Please contact Bitnet support for a username and password.
Example call (retrieving funeral cases): https://app.bit-net.se/api/boa/funeral/cases?startDate=2020-01-01&endDate=2021-01-20&limit=500
Once your integration is activated, a few test offices will be automatically connected to it so that you can start testing the API.
Privileges
You will be granted a certain set of privileges relating to what you can access e.g. customers, legal cases and urns. An endpoint where you can see which privileges you currently have is available through the Access category
Connected Offices
An administrator for a subgroup is able to specify that they want to share their data with you trough a GUI in Bitnet. This is done on a subgroup (undergrupp) level, and all the offices of the subgroup will thus
...
Contact
- Name: API support
- Name: poya@bitnet.nu
- Contact API maintainers
License
- Name: Apache 2.0
- See 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 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 133 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.3 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!