Load Balancer API Quick Reference
Quick description of the different API functions used to manage the Load Balancer
Quick description of the different API functions used to manage the Load Balancer
This section briefly describes the main functions of the API for the OVH Load Balancer under /ipLoadbalancing
Attention, for compatibility reasons the entry point of the old OVH Load Balancer system is still present in the /ip/loadBalancing API, not to be confused with the new /ipLoadbalancing.
For a complete reference to the API functions of the OVH Load Balancer service, it's here
The Frontend, Farm and Server are specific to the protocol (among HTTP, TCP or UDP) in which they are defined. Although they can be "combined" with each other, this is only possible within the same protocol. of the same protocol. Thus, it is not possible to use a Frontend UDP with an HTTP Farm. But it is possible (in the absence of other limitation) to use an HTTP Frontend with an HTTP Farm.
As you can see, each category consists of 3 API functions. It is necessary to properly execute the API function that corresponds to the type of service you want.
As for the frontend, each category is composed of 3 API functions. It is necessary to execute the API function that corresponds to the type of service desired.
As for the frontend and farm, each category is composed of 3 API functions. It is necessary to properly execute the API function that corresponds to the type of the desired service.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community