The Hypertext Transfer Protocol (HTTP)* enables communications between clients and servers. It works as a request-response protocol where a client (browser) sends an HTTP request to a a server which then returns a response to the client. The response contains both status information on the request and may also contain requested content.

Method

Description

Results in:

GET

Using the GET you can obtain data from the web server. It is the most common method used for most Endpoints.

Normally returns a webpage.

DELETE

Using the DELETE method you can delete data over the Betty Blocks API.

Removes targeted data.

HEAD

Using the HEAD method you can check what is returned with a GET before making a GET request. For example, before downloading a large file or response body.

Identical to GET, but without the response body.

OPTIONS

Using the OPTIONS you can check which request methods are supported by a specific Endpoint.

Describes the communication options for the target resource.

POST

Using the POST method, you can post data to the target web server. Data is sent to a server for creating/updating a resource.

Combine this method with Actions to alter or delete data from the Back Office.

PUT

Using the PUT method you can update data over the Betty Blocks API.

Sends data to a server to create/update a resource.

Hypertext Transfer Protocol (HTTP)

HTTP is a protocol defining the order and syntax for information transferred over a network. Requests and responses are the two main kinds of HTTP messages.

All requests and responses can be read by anyone monitoring the session.

Hypertext Transfer Protocol Secure (HTTPS)

HTTPS protocol is an extension of HTTP for providing an encrypted connection between a web server and a browser over Transport Layer Security (TLS). TLS uses a public key encryption technology based on a public and a private key. Requests and response are encrypted with session keys so that any intercepted communication is displayed as a random string of characters and not the plaintext.