Definitions for terms used in our API documentation.
Application program interface (API) is a set of routines, protocols, and tools for building software applications. An API specifies how software components should interact.
An authorization code passed in to an API request via a header or parameter to identify the requester.
Identifying the user of the API. Common techniques for authentication include API Keys.
Callbacks are a feature that allows our system to automatically notify your server whenever certain events happen. When a callback is invoked, it sends a message containing information about the event in question to a specified URL.
The client is the initiating party that sends an API request.
The endpoint is the URL where our API service can be accessed by a client application. The same web service can have multiple endpoints, for example in order to make it available using different protocols.
The header is what's sent preceeding the body of an HTTP request or response.
The part of an API request that tells the server what the client wants to do.
In the API, the client sends the server a request to do something.
After the server receives a request from the client, it attempts to fulfill the request and send the client back a response.
Representational state transfer (REST) is an architectural pattern for interacting with resources via HTTP methods.
The server is software or hardware that provides a service by responding to requests across a network.
The Unique Resource Identifier.
Web Service is used to describe an API that is accessible over the internet through HTTP.
WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information.
XML-RPC is a simple, portable way to make remote procedure calls over HTTP.