protection:write scope. The supplied specification does not define the sync result’s structure.
Requests require a valid bearer token and JSON bodies where applicable. See Overview for authentication and general conventions, and Errors for status and rate-limit details. This group shares the Protection and Services and invoices context.
The addresses
198.51.100.0/24, 192.0.2.10, and 192.0.2.11 are documentation examples. Replace them with your authorized prefix and reachable router endpoint. Replace every path placeholder with its actual resource ID before sending a request.Base URL
Authentication
All requests must include the API key as a bearer token:Push current configuration
Re-applies the current set of prefixes and tunnels for a service to the network.Path parameters
Request
No request body.Example
Add a prefix
Adds an authorized prefix to a protected service.Path parameters
Body parameters
Example
Remove a prefix
Removes a prefix from a protected service. This change takes effect immediately.Path parameters
Example
Create a tunnel
Creates a GRE tunnel to a router endpoint for a protected service.Path parameters
Body parameters
Example
The semantics of an empty
prefixIds array are unspecified. Do not assume it means all prefixes or no prefixes.Update a tunnel
Updates an existing tunnel’s label, endpoint, or associated prefixes.Path parameters
Body parameters
Example
The semantics of an empty
prefixIds array are unspecified. Do not assume it means all prefixes or no prefixes.