DEV API (beta) (ranked 4 of 5138)https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/DEV_API_beta__5e84256b_c406_4b0f_8263_de28b8a00eaa_yaml.yaml
Access Forem articles, users and other resources via API.
For a real-world example of Forem in action, check out DEV.
All endpoints that don't require authentication are CORS enabled.
Dates and date times, unless otherwise specified, must be in
the RFC 3339 format.
- Name: DEV Team
- Name: email@example.com
- Contact API maintainers
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
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 22.2 ms .
Get p50 under 220 ms to get a 4/5 score.
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.
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.3 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
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!