A brief list of terms as used in the API Blueprint context.
Refer to W3C Glossary of Terms for Device Independence for additional terms.
An HTTP transaction (a request-response transaction).
Actions are specified by a HTTP request method within a resource.
An HTTP Application programming interface. Might refer to an API description. See API Blueprint.
The API Blueprint language. A format used to describe API in an API blueprint file.
Atomic data. Most often representing one resource representation in the form of message-body or its validation schema.
An API description. A blueprint file (or a set of files) that describes an API using the API Blueprint language.
An HTTP transaction message.
An asset representing HTTP transaction message body.
An asset representing HTTP transaction message header.
An URI template variable. Also a message-body key (field/object) where applicable.
A HTTP transaction message as well as its discussion, parameters description and any additional related assets such as a validation schema.
A payload may have its identifier – a string for a request payload or an HTTP status code for a response payload.
A payload containing one specific HTTP Request.
A payload containing one specific HTTP Response.
An API resource specified by its URI. It can also refer to a set of resources matching one URI template.
One manifestation of a resource in the form of a payload.
A set of API resources its URI matches one specific URI template.
A validation schema in a form of an asset used to validate (or describe) a message-body.
A compact sequence of characters for describing a range of Uniform Resource Identifiers through variable expansion, see RFC 6570.