├── .gitignore ├── terms ├── Server.md ├── URI.md ├── GET.md ├── Gateway.md ├── Host.md ├── POST.md ├── PUT.md ├── Protocol.md ├── DELETE.md ├── Mashup.md ├── SSL.md ├── Set-Cookie.md ├── Collection.md ├── h-card.md ├── Stateless.md ├── MediaType.md ├── Proxy.md ├── Cache.md ├── Expires.md ├── HTTP.md ├── Header.md ├── Latency.md ├── RDF.md ├── SemanticContent.md ├── CollectionsJSON.md ├── Endpoint.md ├── HTTPMethod.md ├── JSONHAL.md ├── Microformat.md ├── Safe.md ├── API.md ├── WebService.md ├── APIKey.md ├── HTTPS.md ├── Parameter.md ├── Rate-Limiting.md ├── Representation.md ├── SOAP.md ├── Etag.md ├── Authentication.md ├── OAuth.md ├── Resource.md ├── CORS.md ├── Pipelining.md ├── cURL.md ├── DOM.md ├── SLA.md ├── Idempotent.md ├── REST.md ├── Last-Modified.md ├── Versioning.md ├── Hypermedia.md ├── Location.md ├── If-Modified-Since.md ├── HATEOAS.md ├── JSONP.md ├── XML.md ├── JSON.md ├── User-Agent.md ├── Client.md ├── Link.md ├── AJAX.md └── StatusCode.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | -------------------------------------------------------------------------------- /terms/Server.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Server 3 | description: The server is software or hardware that provides a service by responding to requests across a network. 4 | --- 5 | 6 | -------------------------------------------------------------------------------- /terms/URI.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: URI 3 | description: Unique Resource Identifier 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/GET.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: GET 3 | description: The HTTP method for retrieving resources from a RESTful API. 4 | --- 5 | 6 | Example using cURL: 7 | curl --request GET 'http://www.google.com' 8 | -------------------------------------------------------------------------------- /terms/Gateway.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Gateway 3 | description: A proxy that translates between protocols. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Host.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Host 3 | description: Header containing the domain name of the request URL. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/POST.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: POST 3 | description: The HTTP method for creating resources with a RESTful API. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/PUT.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: PUT 3 | description: The HTTP method for updating resources with a RESTful API. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Protocol.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Protocol 3 | description: A defined way of transferring data between peers. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/DELETE.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Delete 3 | description: The HTTP method for deleting resources with a RESTful API. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Mashup.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Mashup 3 | description: Combining multiple APIs to create a new web application. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/SSL.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: SSL 3 | description: A cryptographic protocol that secures traffic on the internet. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Set-Cookie.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Set-Cookie 3 | description: Header that sets a cookie on the client side. 4 | --- 5 | 6 | 7 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Collection.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Collection 3 | description: An API resource that groups other resources together. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/h-card.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: h-card 3 | description: A microformat for embedding data about people or organizations. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Stateless.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Stateless 3 | description: The server doesn't store client context in between requests. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/MediaType.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Media Type 3 | description: Identifier used to indicate the type of data that a file contains. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Proxy.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Proxy 3 | description: An intermediary for requests from clients and servers providing resources. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Cache.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Cache 3 | description: A collection of responses that are reused by the client to improve performance. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Expires.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Expires 3 | description: A header that tells the client it may cache a response until a certain time. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/HTTP.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: HTTP 3 | description: Hypertext Transfer Protocol is how websites and APIs communicate over the internet. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Header.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Header 3 | description: The header is what's sent preceeding the body of an HTTP request or response. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Latency.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Latency 3 | description: The time it takes for the API request to go from the request to the response. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/RDF.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: RDF 3 | description: Resource Description Framework. Framework that is focused on semantic content. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/SemanticContent.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Semantic Content 3 | description: Adding meaning to web resources through the use of specialized tags. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/CollectionsJSON.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Collection+JSON 3 | description: A hypermedia-type for the management and querying of simple collections. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Endpoint.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Endpoint 3 | description: The URI that goes after the base URL and points towards the requested API functionality. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/HTTPMethod.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: HTTP Method 3 | description: The part of an HTTP request that tells the server what the client wants to do. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/JSONHAL.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: JSON+HAL 3 | description: A hypermedia-type which normalizes the hyperlinking and the embedding of resources. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/Microformat.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Microformat 3 | description: An industry standard of semantic markup used to describe the contents of a document. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Safe.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Safe 3 | description: When calling a method on a resource would be the same as doing nothing. GET is a safe method. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/API.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: API 3 | description: Programming Interfaces enable software to interact with other software through exposed functionality. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/WebService.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Web Service 3 | description: Web Service is used to describe an API that is accessable over the internet through HTTP. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/APIKey.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: API Key 3 | description: An authorization code passed in to an API request via a header or parameter to identify the requester. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/HTTPS.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: HTTPS 3 | description: Hypertext Transfer Protocol Secure is how websites and APIs communicate securely over the internet. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/Parameter.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Parameter 3 | description: A parameter is an argument sent to the API which helps define the request and expected response. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Rate-Limiting.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Rate-Limiting 3 | description: Limiting the consumption of an API to a certain number of requests per period of time. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Representation.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Representation 3 | description: Data that describes the state of a resource. Often the body of an HTTP request/response. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/SOAP.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: SOAP 3 | description: Simple Object Access Protocol is a specification for exchanging structured information over the internet. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Etag.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Entity Tag 3 | description: Header which designates a version of a representation. Useful for caching and/or conditional requests. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/Authentication.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Authentication 3 | description: Identifying the user of the API. Common techniques for authentication include API Keys and OAuth. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/OAuth.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: OAuth 3 | description: Open standard authorization framework. Grants access on behalf of an end-user without directly sharing credentials. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Resource.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Resource 3 | description: A resource is some object or entity that has a URI where it can be manipulated through HTTP requests. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/CORS.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: CORS 3 | description: Cross Origin Requests allow javascript in websites to do AJAX requests to domains beyond the one initiating the request. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Pipelining.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Pipelining 3 | description: The client sends several HTTP requests at once and the server responds in the order it receives the requests. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/cURL.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: cURL 3 | description: Command Line Interface to HTTP. Extremely popular for testing APIs and the building block for many client libraries. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/DOM.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: DOM 3 | description: The Document Object Model defines a standard way to represent and interact with objects within both HTML & XML documents. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/SLA.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: SLA 3 | description: Service Level Agreements are a form of contract between a service provider and consumer defining expected performance metrics. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Idempotent.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Idempotent 3 | description: When the side-effects of multiple requests are the same as a single request. GET, PUT, and DELETE are idempotent methods. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/REST.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: REST 3 | description: Representational state transfer is an architectural pattern for interacting with resources via HTTP methods. 4 | type: Acronym 5 | --- 6 | 7 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 8 | -------------------------------------------------------------------------------- /terms/Last-Modified.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Last-Modified 3 | description: Header which tells client the last time representation changed. Important for conditional If-Modified-Since requests. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Versioning.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Versioning 3 | description: Assinging a unique identifier to keep track of the state of the API. If changes are made to the API, the version should change. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Hypermedia.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Hypermedia 3 | description: Any content type which allows entities to link to each other in a standardized way, making other entities discoverable from a client. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/Location.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Location 3 | description: Header which provides information about the location of a newly created resource or which asks web browser to load a different web page. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/If-Modified-Since.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: If-Modified-Since 3 | description: Header which asks to get a representation only if the representation has changed since last request. Used for conditional GET requests. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/HATEOAS.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: HATEOAS 3 | description: Hypermedia as the Engine of Application State is feature of the REST architecture allowing the client to navigate through hypermedia exposed by the API. 4 | type: Acronym 5 | --- 6 | 7 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 8 | -------------------------------------------------------------------------------- /terms/JSONP.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: JSONP 3 | description: JSON with Padding is a technique used to overcome the cross-domain restrictions imposed by browsers to allow data to be retrieved from systems other than the one the page was served by. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... -------------------------------------------------------------------------------- /terms/XML.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: XML 3 | description: Extensible markup language is a format that is used to describe documents and data. 4 | --- 5 | 6 | ``` 7 | 8 | 9 | Montana Flynn 10 | XML 11 | XML 12 | 13 | true 14 | Example XML 15 | 16 | ``` 17 | -------------------------------------------------------------------------------- /terms/JSON.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: JSON 3 | description: Javascript Object Notation is a data format commonly used for APIs requests parameters and response body. 4 | type: Acronym 5 | --- 6 | 7 | ``` 8 | { 9 | "title": "Example JSON", 10 | "published": true, 11 | "entry": { 12 | "term": "JSON", 13 | "description": "Javascript Object Notation", 14 | "Author": "Montana Flynn" 15 | } 16 | } 17 | ``` 18 | -------------------------------------------------------------------------------- /terms/User-Agent.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: User-Agent 3 | description: Header which lets the server know what kind of software is making the request. It contains information about the user agent originating the request. This header should be used for statistical purposes or automated user agent recognition to handle the particular software limitations. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/Client.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Client 3 | description: The client is the initiating party that sends an API request. Often times there will be many clients consuming the same API. 4 | --- 5 | 6 | A client is anything that can obtain a service provided by another server. Fat Clients are clients that performs the majority of the logic and data processing itself, while a Thin Client presents preprocessed data to the viewer. 7 | 8 | There can be many clients consuming a single API. 9 | 10 | ![Client Diagram](http://i.imgur.com/EVuUjWW.png "Client Diagram) 11 | -------------------------------------------------------------------------------- /terms/Link.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Link 3 | description: A fully-qualified HTTP address for a particular resource (e.g., "http://my.api.com/v1/resources/resource-name"). RESTful APIs by definition should provide links from a resource to all related resources and collections which provide subsequent actions using the resource. This allows for an API to be traversed organically and for an application developer to ensure his API Client is not in (as much) jeopardy if a resource's location changed. 4 | --- 5 | 6 | Here you can put detailed markdown content such as examples, diagrams, related terms, etc... 7 | -------------------------------------------------------------------------------- /terms/AJAX.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Ajax 3 | description: Originally an acronym, Asynchronous JavaScript and XML, allows the client to send & retrieve data from the server without reloading the page. 4 | --- 5 | 6 | Ajax is not a single piece of technology but rather a group of related technologies that are used to create dynamic and interactive web applications. Most often XML is replaced with HTML or JSON as the data format. 7 | 8 | ``` 9 | var r = new XMLHttpRequest(); 10 | r.open("POST", "path/to/api", true); 11 | r.onreadystatechange = function () { 12 | if (r.readyState != 4 || r.status != 200) return; 13 | alert("Success: " + r.responseText); 14 | }; 15 | r.send("Non Stop!"); 16 | ``` 17 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # API Glossary 2 | An educational and collaborative project with the mission to help define a new API industry. 3 | 4 | - Get the foundational knowledge you need to dive right into API use, design, and development. 5 | - Explain APIs and related technology to nontechs, without mumbling something from the RFC. 6 | - Develop your own API using industry leading standards, design patterns and documentation. 7 | 8 | ## Contributing 9 | 10 | *Any and all feedback, suggestions and lively discussions are highly encouraged.* 11 | 12 | Everyone is welcome to contribute by submitting a pull request, opening an issue or sharing the project. Existing terms are located in the [`terms`](https://github.com/Mashape/apiglossary/tree/master/terms "View existing terms or add your own.") directory and described using YAML frontmatter & markdown. Please make sure filenames contain no spaces and end with the `.md` extension. 13 | 14 | ```md 15 | --- 16 | term: Term 17 | description: A short description of the term that will be used on the index. 18 | --- 19 | 20 | ## GitHub Flavored Markdown 21 | Where you can put detailed content such as examples, diagrams, related terms, etc... 22 | ``` 23 | 24 | ![API Cat](http://i.imgur.com/6KTUN42.jpg "Core Contributer") 25 | -------------------------------------------------------------------------------- /terms/StatusCode.md: -------------------------------------------------------------------------------- 1 | --- 2 | term: Status Code 3 | description: HTTP status codes are what the server sends in the response back to the client with regards to the status of the request. 4 | --- 5 | 6 | - 100 "continue" 7 | - 101 "switching protocols" 8 | - 102 "processing" 9 | - 200 "ok" 10 | - 201 "created" 11 | - 202 "accepted" 12 | - 203 "non-authoritative information" 13 | - 204 "no content" 14 | - 205 "reset content" 15 | - 206 "partial content" 16 | - 207 "multi-status" 17 | - 300 "multiple choices" 18 | - 301 "moved permanently" 19 | - 302 "moved temporarily" 20 | - 303 "see other" 21 | - 304 "not modified" 22 | - 305 "use proxy" 23 | - 307 "temporary redirect" 24 | - 400 "bad request" 25 | - 401 "unauthorized" 26 | - 402 "payment required" 27 | - 403 "forbidden" 28 | - 404 "not found" 29 | - 405 "method not allowed" 30 | - 406 "not acceptable" 31 | - 407 "proxy authentication required" 32 | - 408 "request time-out" 33 | - 409 "conflict" 34 | - 410 "gone" 35 | - 411 "length required" 36 | - 412 "precondition failed" 37 | - 413 "request entity too large" 38 | - 414 "request-uri too large" 39 | - 415 "unsupported media type" 40 | - 416 "requested range not satisfiable" 41 | - 417 "expectation failed" 42 | - 418 "i'm a teapot" 43 | - 422 "unprocessable entity" 44 | - 423 "locked" 45 | - 424 "failed dependency" 46 | - 425 "unordered collection" 47 | - 426 "upgrade required" 48 | - 428 "precondition required" 49 | - 429 "too many requests" 50 | - 431 "request header fields too large" 51 | - 500 "internal server error" 52 | - 501 "not implemented" 53 | - 502 "bad gateway" 54 | - 503 "service unavailable" 55 | - 504 "gateway time-out" 56 | - 505 "http version not supported" 57 | - 506 "variant also negotiates" 58 | - 507 "insufficient storage" 59 | - 509 "bandwidth limit exceeded" 60 | - 510 "not extended" 61 | - 511 "network authentication required" 62 | --------------------------------------------------------------------------------