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:
Accounts: for user management
Configs: for administration of configurations, the fundamental internal data structure
Data queries: for API access to traffic data
Database: for management of versioning
Planets: for planet-level settings such as interactive challenges
Tags: for retrieval of tag data
Tools: for miscellaneous capabilities
Namespaces for security settings
ACL Profiles
Actions
Content Filter Profiles
Content Filter Rules
Dynamic Rules
Flow Control Policies
Global Filters
Rate Limit Rules
Security Policies
Namespaces for site-related settings
Backend Services
Certificates
Edge Functions
Load Balancers
Proxy Templates
Server Groups
Namespaces for other capabilities
Accounts
Configs
Data queries
Database
Planet
Tags
Tools
Last updated