Link11 WAAP
v5
v5
  • Link11 WAAP Documentation
  • Release Notes
  • Known Issues
  • User Guide
    • Introduction to Link11 WAAP
  • How Link11 WAAP Works
    • Traffic Filtering Process
    • Traffic Reporting and Analytics
    • Policy Mapping and Traffic Routing
    • Tagging
    • UI Overview and Common Elements
  • Console UI Walkthrough
    • Analytics
      • Dashboard
      • Events Log
    • Security
      • Global Filters
      • Flow Control Policies
      • Security Policies
      • Rate Limit Rules
      • ACL Profiles
      • Actions
      • Dynamic Rules
      • Quarantined
      • Content Filter
        • Content Filter Profiles
        • Content Filter Rules
    • Sites
      • Server Groups
      • Proxy Templates
      • Mobile Application Groups
      • Backend Services
      • Edge Functions
      • DNS Records
      • SSL
        • Load Balancers
        • Certificates
    • System
      • Interactive Challenge
      • SSO Configuration
      • Purge CDN Cache
      • Users Management
      • Security Alerts
      • Log Exporters
      • Version Control
      • System DB
      • Publish Changes
    • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Authenticate mobile app users
      • Ban, unban, and allowlist traffic sources
      • Bypass Link11 WAAP for loadtesting or other purposes
      • Configure a new path/section of a site
      • Control caching behavior
      • Enable GraphQL traffic
      • Enable mTLS (mutual TLS)
      • Protect sensitive information in logs and analytics
      • Quickly block an attacker
      • Redirect or block HTTP traffic
      • Run custom code
      • Set rate limits and exemptions
      • Stream event data to a SIEM solution or other destination
    • The Link11 WAAP API
      • Overview
      • Internal data structures
      • Using Swagger UI
      • Using curl
  • Reference Information
    • Acronyms
    • API
      • API access to traffic data
      • Types of namespaces
      • Namespace reference
        • ACL Profiles
        • Actions
        • Backend Services
        • Certificates
        • Configs
        • Content Filter Profiles
        • Content Filter Rules
        • Data queries
        • Dynamic Rules
        • Edge Functions
        • Flow Control Policies
        • Global Filters
        • Load Balancers
        • Log Exporters
        • Mobile Application Groups
        • Planets
        • Proxy Templates
        • Rate Limit Rules
        • Security Alerts
        • Security Policies
        • Server Groups
        • Tags
        • Tools
        • Users
    • Hostile Bot Detection / LWCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Log Exporter Output
    • Pattern Matching Syntax
    • Query Filter Syntax and Best Practices
  • Support
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Reference Information
  2. API
  3. Namespace reference

Backend Services

PreviousActionsNextCertificates

Last updated 5 months ago

Was this helpful?

Delete Backend Services

delete

Delete all Backend Services in a configuration

Path parameters
configstringRequired
Responses
200
Backend Services deleted successfully
application/json
422
Validation Error
application/json
delete
DELETE /api/v4.0/conf/{config}/backend-services HTTP/1.1
Host: 
Accept: */*
{
  "message": "Successfully deleted entry"
}

Get single Backend Service

get

Get an individual Backend Service from the specified configuration

Path parameters
configstringRequired
entry_idstringRequired
Responses
200
Backend Service retrieved successfully
application/json
422
Validation Error
application/json
get
GET /api/v4.0/conf/{config}/backend-services/{entry_id} HTTP/1.1
Host: 
Accept: */*
{
  "back_hosts": [
    {
      "backup": true,
      "down": true,
      "fail_timeout": 1,
      "host": "text",
      "http_ports": [
        80,
        8080
      ],
      "https_ports": [
        443,
        8443
      ],
      "max_fails": 1,
      "monitor_state": "text",
      "weight": 1
    }
  ],
  "description": "",
  "http11": true,
  "id": "text",
  "least_conn": true,
  "name": "text",
  "sticky": "none",
  "sticky_cookie_name": "",
  "transport_mode": "default"
}

Delete single Backend Service

delete

Delete an individual Backend Service from the specified configuration

Path parameters
configstringRequired
entry_idstringRequired
Responses
200
Backend Service deleted successfully
application/json
422
Validation Error
application/json
delete
DELETE /api/v4.0/conf/{config}/backend-services/{entry_id} HTTP/1.1
Host: 
Accept: */*
{
  "message": "Successfully deleted entry"
}

Get Backend Services version list

get

Get list of versions of Backend Services in a configuration

Path parameters
configstringRequired
Responses
200
Backend Services version list retrieved successfully
application/json
422
Validation Error
application/json
get
GET /api/v4.0/conf/{config}/backend-services/versions HTTP/1.1
Host: 
Accept: */*
{
  "total": 1,
  "items": [
    {
      "author": "text",
      "email": "name@gmail.com",
      "message": "text",
      "date": "2025-05-18T00:26:39.991Z",
      "version": "42bcc1282349db1e5791484c3d69420b1d8a8bc1",
      "parents": [
        "f44073242093228b45bff7eb7a065559fa9b46aa"
      ]
    }
  ]
}

Get version of Backend Service

get

Get a specific version of a Backend Service

Path parameters
configstringRequired
versionstringRequired
Responses
200
Backend Service retrieved successfully
application/json
422
Validation Error
application/json
get
GET /api/v4.0/conf/{config}/backend-services/versions/{version} HTTP/1.1
Host: 
Accept: */*
{
  "total": 1,
  "items": [
    {
      "back_hosts": [
        {
          "backup": true,
          "down": true,
          "fail_timeout": 1,
          "host": "text",
          "http_ports": [
            80,
            8080
          ],
          "https_ports": [
            443,
            8443
          ],
          "max_fails": 1,
          "monitor_state": "text",
          "weight": 1
        }
      ],
      "description": "",
      "http11": true,
      "id": "text",
      "least_conn": true,
      "name": "text",
      "sticky": "none",
      "sticky_cookie_name": "",
      "transport_mode": "default"
    }
  ]
}

Revert a Backend Service to the specified version

put

Set a previous Backend Service version to be the current one

Path parameters
configstringRequired
versionstringRequired
Responses
200
Backend Service reversion was successful
application/json
422
Validation Error
application/json
put
PUT /api/v4.0/conf/{config}/backend-services/versions/{version}/revert HTTP/1.1
Host: 
Accept: */*
{
  "message": "Successfully updated entry"
}
  • GETGet Backend Services
  • PUTModify Backend Services
  • POSTCreate Backend Services
  • DELETEDelete Backend Services
  • GETGet single Backend Service
  • PUTModify a single Backend Service
  • POSTCreate single Backend Service
  • DELETEDelete single Backend Service
  • GETGet Backend Services version list
  • GETGet version of Backend Service
  • PUTRevert a Backend Service to the specified version

Get Backend Services

get

Get all Backend Services in a configuration

Path parameters
configstringRequired
Responses
200
Backend Services retrieved successfully
application/json
422
Validation Error
application/json
get
GET /api/v4.0/conf/{config}/backend-services HTTP/1.1
Host: 
Accept: */*
{
  "total": 1,
  "items": [
    {
      "back_hosts": [
        {
          "backup": true,
          "down": true,
          "fail_timeout": 1,
          "host": "text",
          "http_ports": [
            80,
            8080
          ],
          "https_ports": [
            443,
            8443
          ],
          "max_fails": 1,
          "monitor_state": "text",
          "weight": 1
        }
      ],
      "description": "",
      "http11": true,
      "id": "text",
      "least_conn": true,
      "name": "text",
      "sticky": "none",
      "sticky_cookie_name": "",
      "transport_mode": "default"
    }
  ]
}

Modify Backend Services

put

Updates an existing set of Backend Services for a configuration

Path parameters
configstringRequired
Body
descriptionany ofOptionalDefault: ""
stringOptional
http11booleanRequired

Use HTTP/1.1

idstringRequired
least_connbooleanRequired
namestring · min: 1Required
stickystring · enumRequired

Load Balancing stickiness model

Possible values:
sticky_cookie_nameany ofRequired

Custom cookie name

Default: ""
stringOptional
transport_modestring · enumRequired

Tranport protocol Service connectivity might follow incoming requests, will always be HTTP, or always HTTPS. Port-bridge mode means that Reblaze will target port numbers identical to incoming requests' port numbers.

Possible values:
Responses
200
Backend Services updated successfully
application/json
422
Validation Error
application/json
put
PUT /api/v4.0/conf/{config}/backend-services HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 315

[
  {
    "back_hosts": [
      {
        "backup": true,
        "down": true,
        "fail_timeout": 1,
        "host": "text",
        "http_ports": [
          80,
          8080
        ],
        "https_ports": [
          443,
          8443
        ],
        "max_fails": 1,
        "monitor_state": "text",
        "weight": 1
      }
    ],
    "description": "",
    "http11": true,
    "id": "text",
    "least_conn": true,
    "name": "text",
    "sticky": "none",
    "sticky_cookie_name": "",
    "transport_mode": "default"
  }
]
{
  "message": "Successfully updated entry"
}

Create Backend Services

post

Create a complete set of Backend Services for a configuration

Path parameters
configstringRequired
Body
descriptionany ofOptionalDefault: ""
stringOptional
http11booleanRequired

Use HTTP/1.1

idstringRequired
least_connbooleanRequired
namestring · min: 1Required
stickystring · enumRequired

Load Balancing stickiness model

Possible values:
sticky_cookie_nameany ofRequired

Custom cookie name

Default: ""
stringOptional
transport_modestring · enumRequired

Tranport protocol Service connectivity might follow incoming requests, will always be HTTP, or always HTTPS. Port-bridge mode means that Reblaze will target port numbers identical to incoming requests' port numbers.

Possible values:
Responses
201
Backend Services created successfully
application/json
422
Validation Error
application/json
post
POST /api/v4.0/conf/{config}/backend-services HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 315

[
  {
    "back_hosts": [
      {
        "backup": true,
        "down": true,
        "fail_timeout": 1,
        "host": "text",
        "http_ports": [
          80,
          8080
        ],
        "https_ports": [
          443,
          8443
        ],
        "max_fails": 1,
        "monitor_state": "text",
        "weight": 1
      }
    ],
    "description": "",
    "http11": true,
    "id": "text",
    "least_conn": true,
    "name": "text",
    "sticky": "none",
    "sticky_cookie_name": "",
    "transport_mode": "default"
  }
]
{
  "message": "Successfully created entry"
}

Modify a single Backend Service

put

Update an individual Backend Service within a configuration

Path parameters
configstringRequired
entry_idstringRequired
Body
descriptionany ofOptionalDefault: ""
stringOptional
http11booleanRequired

Use HTTP/1.1

idstringRequired
least_connbooleanRequired
namestring · min: 1Required
stickystring · enumRequired

Load Balancing stickiness model

Possible values:
sticky_cookie_nameany ofRequired

Custom cookie name

Default: ""
stringOptional
transport_modestring · enumRequired

Tranport protocol Service connectivity might follow incoming requests, will always be HTTP, or always HTTPS. Port-bridge mode means that Reblaze will target port numbers identical to incoming requests' port numbers.

Possible values:
Responses
200
Backend Service updated successfully
application/json
422
Validation Error
application/json
put
PUT /api/v4.0/conf/{config}/backend-services/{entry_id} HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 313

{
  "back_hosts": [
    {
      "backup": true,
      "down": true,
      "fail_timeout": 1,
      "host": "text",
      "http_ports": [
        80,
        8080
      ],
      "https_ports": [
        443,
        8443
      ],
      "max_fails": 1,
      "monitor_state": "text",
      "weight": 1
    }
  ],
  "description": "",
  "http11": true,
  "id": "text",
  "least_conn": true,
  "name": "text",
  "sticky": "none",
  "sticky_cookie_name": "",
  "transport_mode": "default"
}
{
  "message": "Successfully updated entry"
}

Create single Backend Service

post

Create an individual Backend Service within a configuration

Path parameters
configstringRequired
entry_idstringRequired
Body
descriptionany ofOptionalDefault: ""
stringOptional
http11booleanRequired

Use HTTP/1.1

idstringRequired
least_connbooleanRequired
namestring · min: 1Required
stickystring · enumRequired

Load Balancing stickiness model

Possible values:
sticky_cookie_nameany ofRequired

Custom cookie name

Default: ""
stringOptional
transport_modestring · enumRequired

Tranport protocol Service connectivity might follow incoming requests, will always be HTTP, or always HTTPS. Port-bridge mode means that Reblaze will target port numbers identical to incoming requests' port numbers.

Possible values:
Responses
201
Backend Service created successfully
application/json
422
Validation Error
application/json
post
POST /api/v4.0/conf/{config}/backend-services/{entry_id} HTTP/1.1
Host: 
Content-Type: application/json
Accept: */*
Content-Length: 313

{
  "back_hosts": [
    {
      "backup": true,
      "down": true,
      "fail_timeout": 1,
      "host": "text",
      "http_ports": [
        80,
        8080
      ],
      "https_ports": [
        443,
        8443
      ],
      "max_fails": 1,
      "monitor_state": "text",
      "weight": 1
    }
  ],
  "description": "",
  "http11": true,
  "id": "text",
  "least_conn": true,
  "name": "text",
  "sticky": "none",
  "sticky_cookie_name": "",
  "transport_mode": "default"
}
{
  "message": "Successfully created entry"
}