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

Partner Integrations (ranked 919 of 5138)

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

GENERAL INFORMATION

CSLogo

<br />

Overview

Various API calls against multiple servers are required for integration to the Compliance Systems API. This site will focus on the most common requests required for a typical integration effort.

<br />

General Concepts

The integration effort may differ scenario by scenario. Ultimately, the end goal is to get a complete/accurate payload to generate documents. This is normally accomplished by aggregating data from 3 sources which include the partner system, Simplicity Config, and Runtime.
<br />

The typical workflow is normally:
<br />

  1. Get payload into the Compliance Systems structure
    <br />
    By far, the most complex effort during the integration is the data structure. Since most partner platforms don't contain an ETL system to support rapid/quick data changes, a common approach is to our the Compliance Systems TDT service. Th

...

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 177 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