Backend Services

Get Backend Services

get

Get all Backend Services in a configuration

Path parameters
configstringRequired
Responses
200

Backend Services retrieved successfully

application/json
get
/api/v4.0/conf/{config}/backend-services

Modify Backend Services

put

Updates an existing set of Backend Services for a configuration

Path parameters
configstringRequired
Bodyobject · BackendService[]
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
put
/api/v4.0/conf/{config}/backend-services

Create Backend Services

post

Create a complete set of Backend Services for a configuration

Path parameters
configstringRequired
Bodyobject · BackendService[]
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
post
/api/v4.0/conf/{config}/backend-services

Delete Backend Services

delete

Delete all Backend Services in a configuration

Path parameters
configstringRequired
Responses
200

Backend Services deleted successfully

application/json
delete
/api/v4.0/conf/{config}/backend-services

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
get
/api/v4.0/conf/{config}/backend-services/{entry_id}

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
put
/api/v4.0/conf/{config}/backend-services/{entry_id}

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
post
/api/v4.0/conf/{config}/backend-services/{entry_id}

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
delete
/api/v4.0/conf/{config}/backend-services/{entry_id}

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
get
/api/v4.0/conf/{config}/backend-services/versions

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
get
/api/v4.0/conf/{config}/backend-services/versions/{version}

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
put
/api/v4.0/conf/{config}/backend-services/versions/{version}/revert

Last updated

Was this helpful?