|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
T2M Release 1 Mulesoft API Proxy (t2m-mule-r1) (ranked 4577 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/UlwIDdh7i2Bb6FdrTa3V5_t2m_release_1_mulesoft_api_proxy__t2m_mule_r1__json.jsonGENERAL INFORMATION
Introduction
<table><tbody><tr><td class = 'into_api' style='border:none;padding:0 0 0 0'><p>The intent of these APIs is to provide a reverse proxy to Mulesoft APIs in order to enable them to have OAuth2 authentication in place. These APIs are exposed by Mulesoft to SFDC to perform account, contact, site & bill profile related activities on downstream systems
Features
The Mulesoft APIs provides the features below.
| Feature | Consumer | Downstream Systems | Description |
|---|---|---|---|
POST account |
SFDC | T2R, ROC, SNOW, VERITAS, CCMS, TIGFIN , ModernERP | Create/ Update the customer accounts in downstream systems. |
POST contact |
SFDC | ROC, SNOW , T2R , IP007A | Create/ Update the customer contacts in downstream systems. |
POST site |
SFDC | SNOW, T2R | Create/ Update the customer sites in downstream systems. |
POST bill-profile |
SFDC | ROC, SNOW , IP007A | Create/ Update the bill profiles in downstream systems. |
...
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 1/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 1,090 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.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!