|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
BulkSMS JSON (ranked 796 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/BulkSMS_JSON_11435ecf_2b6c_4102_b4ad_2d7ed209247b_json.jsonGENERAL INFORMATION
Overview
The JSON REST API allows you to submit and receive BulkSMS messages. You can also get access to past messages and see your account profile.
The base URL to use for this service is https://api.bulksms.com/v1. The base URL cannot be used on its own; you must append a path that identifies an operation and you may have to specify some path parameters as well.
Click here to go to the main BulkSMS developer site.
In order to give you an idea on how the API can be used, some JSON snippets are provided below. Have a look at the messages section for more information.
Probably the most simple example
{
"to": "+27001234567",
"body": "Hello World!"
}
You can send unicode automatically using the auto-unicode query parameter.
Alternatively, you can specify UNICODE in the request body. Here is an example that sets the encoding explicitly
{
"to": "+27001234567",
"body": "Dobrá práce! Jak se máš?",
...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: A05:2021
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 93.6 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 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!