|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Apacta (ranked 3687 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Apacta_9988034a_583c_4aab_b75f_50db33e44617_json.jsonGENERAL INFORMATION
API for a tool to craftsmen used to register working hours, material usage and quality assurance.
Endpoint
The endpoint https://app.apacta.com/api/v1 should be used to communicate with the API. API access is only allowed with SSL encrypted connection (https).
Authentication
URL query authentication with an API key is used, so appending ?api_key={api_key} to the URL where {api_key} is found within Apacta settings is used for authentication
Pagination
If the endpoint returns a pagination object it means the endpoint supports pagination - currently it's only possible to change pages with ?page={page_number} but implementing custom page sizes are on the road map.
Search/filter
Is experimental but implemented in some cases - see the individual endpoints' docs for further explanation.
Ordering
Is currently experimental, but on some endpoints it's implemented on URL querys so eg. to order Invoices by invoice_number appending `?sort=Invoices.invoice_number&direction
...
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 593 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 2.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!