|API RANK| by Escape.tech

Benchmark and ranking of 5138+ public APIs by Escape.tech

Back to the list Request ranking update

GENERAL INFORMATION

<div class="smtp2go-doc-container">

<h1>SMTP2GO API Documentation</h1>

<h3>API Information</h3>

<p>
	The SMTP2GO API's base URL is <strong>https&#58;//api.smtp2go.com/v3/</strong><br />
	Any API URLs will always be relative to this URL.
</p>

<p>
	For example, an API call to <strong>/stats/email_summary</strong> will be reachable at <strong>https&#58;//api.smtp2go.com/v3/stats/email_summary</strong>
</p>

<h3>Technical Details</h3>

<p>
	The API has the following characteristics:
</p>

<ul>
	<li>All API Calls must be made with an <strong>HTTP POST</strong> request.</li>
	<li>All <strong>input to</strong> and <strong>output from</strong> the API is made using JSON objects.</li>
	<li>All input payloads <strong>MUST</strong> contain the <strong>'api_key'</strong> field.</li>
	<li>All calls return a <strong>JSON</strong> payload consisting of a result string and any data that was returned.</li>
	<li>Any <strong>200 OK</strong> responses indicate a successful call. Err

...

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 3/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 282 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!

Last scanned: 5/4/2023