VOOZH about

URL: https://apistylebook.com/design/topics/http-status-200

⇱ 200 OK


200 OK

Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.

Agenzia per l'Italia Digital & Team per la trasformazione digital (Italian administration) - Interoperability model for the Public Administration

REST interface processing rules

Atlassian - Atlassian REST API Design Guidelines version 1

Appendix A: Response Codes

Australian Digital Transformation Office - API Design Guide

GET /magazines
PUT /magazines
DELETE /magazines
DELETE /magazines/1234
HEAD /magazines
HEAD /magazines/1234

Cloud Foundry - Cloud Controller API v3 Style Guide (Proposal)

Successful Requests

Deliveroo - API Design

PATCH, mutating entities
200 OK, if the modification succeeded
Return codes and errors
POST and PATCH should never result in a 200 (generally 201, occasionally 202).
Caching
Responses with the following status codes should specify a Cache-Control header

Haufe - Haufe API style guide

HTTP Status (Get List of resources)
HTTP Status (Read Single Resource)
HTTP Status Codes

Heroku - HTTP API Design Guide

Return appropriate status codes

PayPal - API Style Guide

HTTP Status (Collections)
HTTP Status (Read Single Resource)

White House - White House Web API Standards

Error handling

Zalando - RESTFul API Guidelines

Success Codes

adidas - adidas API design guidelines

Asynchronous Tasks
Security