API
This page describes Reblaze's API namespaces and endpoints. It assumes you are already familiar with the information contained here, about internal data structures and API usage.
This page is provided for reference purposes. By default, every Reblaze planet includes an instance of Swagger UI, which provides this same information with additional interactive features (building curl commands, submitting API calls directly, etc). Read more about this.
API namespaces: overview
The various namespaces within the API can be organized into three categories of settings. The category listings below include links to more information about the settings themselves; the API calls are documented below.
Namespaces for security settings:
Namespaces for site-related settings:
Backend Services (the services that Reblaze is protecting)
Certificates (for managing SSL certificates)
Edge Functions (for running custom Lua code)
Load Balancers (managing SSL associated with load balancers)
Proxy Templates (parameters for the overall architecture of Reblaze)
Server Groups (site-level properties)
Namespaces for other capabilities:
Configs: for administration of configurations, the fundamental internal data structure
Data queries: for API access to traffic data and managing quarantined traffic sources.
Database: for management of versioning
Planets: for planet-level settings such as interactive challenges
Tags: for retrieval of tag data
Tools: for miscellaneous capabilities
Users: for management of users and API keys
Namespaces in alphabetical order
ACL Profiles
Actions
Backend Services
Certificates
Configs
Content Filter Profiles
Content Filter Rules
Data queries
Two of the Data queries routes below manage quarantined traffic sources. The rest are for retrieving traffic data; see API Access to Traffic Data for instructions on using them.
Dynamic Rules
Edge Functions
Flow Control Policies
Global Filters
Load Balancers
Planets
Proxy Templates
Rate Limit Rules
Security Policies
Server Groups
Tags
Tools
Users
Last updated