Introduction
The LeafLink API offers a REST-like programmatic interface to the LeafLink platform. We provide a predictable JSON request/response structure and use typical HTTP codes and methods.
The API is available at https://api.leaflink.com.
Content Type
All LeafLink API endpoints use a content type of application/json.
Example:
curl --header "Content-Type: application/json" https://api.leaflink.com/<PATH>
Naming Conventions
LeafLink API uses snake_case naming for paths, query parameters, and object attributes. Incorrect names will generally result in a 400 Bad Request or 404 Not Found code, depending on the offense.
All endpoint paths do not end with a trailing slash. If a trailing slash is included, 404 Not Found code is returned.
CORS
The LeafLink API does not allow for cross origin requests. Any attempts to communicate with the API via browser will fail preflight checks.