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

Import API (ranked 127 of 5138)

https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Import_API_511fcb8f_e94b_43df_8c7e_60182fc41d2f_yaml.yaml

GENERAL INFORMATION

Introduction

The CARTO Import API allows you to upload files to a CARTO account, check on their current upload status, as well as delete and list importing processes on a given account. This API consists of several HTTP requests targeted at a set of CARTO endpoints that deal with the conversion and import of the sent files. CARTO tables can be classified as Standard Tables or Sync Tables. Additionally, the ArcGIS Server™ Connector enables you to import ArcGIS™ layers into your datasets.

Authorization

In order to access Maps API you must provide an API key. The CARTO Authorization guide explains how these keys are sent (TLDR: HTTP basic auth or query string param with the API key token). Depending on the permissions granted to the provided API key, the request will be authorized or not.

Contact

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 466 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 4/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 4/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