> ## Documentation Index > Fetch the complete documentation index at: https://docs.advinservers.com/llms.txt > Use this file to discover all available pages before exploring further. # List locations for floating IPs > ### Overview Lists locations where the current team has servers and can request a floating IP address. `prices` lists the price of each IP family, so you can show prices before requesting a quote. A `null` price means the price could not be loaded, and buying that family will be refused with a reason. ### Permissions Requires the `network.read` (View networking) permission for the selected team. Resources outside that team return 404. ## OpenAPI ````yaml https://console.advinservers.com/docs/openapi.json get /floating-ips/locations openapi: 3.1.0 info: title: API reference version: 1.0.0 description: >- Use this API to manage your team's servers, networks, backups, and other resources. ## Authentication Create an API key under **API Keys** and send it as a bearer token with every request: ``` Authorization: Bearer {YOUR_API_KEY} Accept: application/json ``` Copy the key when you create it. It cannot be shown again. Revoking a key takes effect immediately. ## Permissions Give each key only the permissions it needs. Every endpoint lists the required permission. Permissions cover servers and other resources in the key's team. ## Team scope A key can access resources in the team selected when it was created. This includes servers, snapshots, backups, firewall groups, images, SSH keys, scripts, networks and addresses. Resources in other teams return `404 Not Found`. Create a separate key for each team. The key determines the team for every request. Legacy keys that had no team are assigned to the account's first owned team. ## Actions that need the panel API keys cannot do the following, even with every permission. Sign in to the panel in a browser to do them: - Create, edit or revoke API keys - Edit the IP groups that restrict API keys - End signed-in sessions - Change two-factor authentication - Change the account's email address - Accept or decline team invitations - Switch or leave a team This keeps a leaked key from widening its own access or locking you out of your account. ## Source IP restrictions A key can be restricted to one or more IP groups. Requests from other addresses are rejected. ## Requests and responses Each endpoint lists its path, query, header, and body parameters. Examples use fictional data. Single records use JSON objects. Collections use JSON arrays unless the endpoint supports pagination. Timestamps use ISO 8601 in UTC. Error responses include `message`. Validation errors also include an `errors` object for each field. Each endpoint lists its status codes. ## Audit log Every API request, including reads, is recorded in the account audit log with the key that made it. servers: - url: https://console.advinservers.com/api/v1/client security: - http: [] tags: - name: Account description: Billing contact details and account setup progress. - name: Account activity description: Actions performed in the current team by people and API keys. - name: Servers description: >- Order and list servers, read their state and resource use, open a console, and control power. - name: Server settings description: >- Rename a server, rebuild it, and change its hardware, media, resolvers and credentials. - name: Backups description: Scheduled server copies stored separately from the server. - name: Snapshots description: >- Take, restore and move server snapshots. Snapshots are kept in snapshot storage that the team buys by the GiB. - name: Firewall groups description: Reusable sets of firewall rules, and the servers they apply to. - name: IP groups description: Reusable source address lists for firewall rules. - name: Server firewall description: >- Read default traffic policies and rules managed outside your firewall groups. - name: IP addresses description: Manage floating IPs and server address assignments. - name: Private networks description: Connect servers over a private network in the same location. - name: Reverse DNS description: Set the hostnames returned by IP address lookups. - name: DDoS protection description: Configure attack filtering for server addresses. - name: Bandwidth description: Buy extra bandwidth and share it between servers or location pools. - name: SSH keys description: Public keys the account can install on a server when it is built. - name: Setup scripts description: Scripts the account can run on a server when it is built. - name: ISO images description: ISO images you have downloaded, and the servers they are mounted on. - name: Server upgrades description: Change an existing server's plan. - name: Checkout description: Choose a payment method and pay for a purchase. - name: Invoices description: View and pay account invoices. - name: Billing description: Manage service renewals, payment methods and account credit. - name: Transfers description: Move resources between teams or transfer ownership. - name: Teams description: Manage the team assigned to your API key. - name: Team members description: Invite people and manage their team access. - name: Team roles description: Define the permissions granted to team members. - name: Team activity description: View actions performed in a team. - name: Support tickets description: >- Open, read, reply to and close support tickets. Tickets belong to the account holder and are not shared with team members. paths: /floating-ips/locations: get: tags: - IP addresses summary: List locations for floating IPs description: >- ### Overview Lists locations where the current team has servers and can request a floating IP address. `prices` lists the price of each IP family, so you can show prices before requesting a quote. A `null` price means the price could not be loaded, and buying that family will be refused with a reason. ### Permissions Requires the `network.read` (View networking) permission for the selected team. Resources outside that team return 404. operationId: floatingIp.locations responses: '200': description: The record, as a JSON object. There is no envelope. content: application/json: schema: type: object examples: - items: - id: 3 name: Kansas City, MO sellable: ipv4: true ipv6: true prices: ipv4: recurring_amount: '3.00' currency: USD billing_cycle: monthly ipv6: recurring_amount: '1.00' currency: USD billing_cycle: monthly properties: items: type: array description: The cities where the account may request an address. examples: - - id: 3 name: Kansas City, MO items: $ref: '#/components/schemas/FloatingIpPurchaseLocationData' sellable: description: Whether IPv4 and IPv6 addresses are available to buy. examples: - ipv4: true ipv6: true allOf: - $ref: '#/components/schemas/FloatingIpSellableData' prices: description: >- Current IPv4 and IPv6 prices for display. Request a quote before buying. examples: - ipv4: recurring_amount: '3.00' currency: USD billing_cycle: monthly ipv6: recurring_amount: '1.00' currency: USD billing_cycle: monthly allOf: - $ref: '#/components/schemas/FloatingIpPricingData' required: - items - sellable - prices '401': description: >- The key was missing, malformed, revoked, or belongs to an account that no longer exists. content: application/json: schema: type: object properties: message: type: string examples: - Unauthenticated. required: - message '403': description: >- Access denied. Check the key's team, permissions and allowed IP addresses. Some actions, such as managing API keys, require a browser session. The response message explains the reason. content: application/json: schema: type: object properties: message: type: string examples: - >- This API key is not allowed to do that in this team. It needs the "snapshot.delete" permission. required: - message '429': description: >- Too many requests. The `Retry-After` header says how many seconds to wait. Limits are per account, so several keys on one account share them. content: application/json: schema: type: object properties: message: type: string examples: - Too Many Attempts. required: - message components: schemas: FloatingIpPurchaseLocationData: type: object description: >- A city the account may buy a floating address in: one it already keeps a server in. examples: - id: 3 name: Kansas City, MO properties: id: type: integer description: The id ID. examples: - 3 name: type: string description: The name shown to customers. examples: - Kansas City, MO required: - id - name title: FloatingIpPurchaseLocationData FloatingIpSellableData: type: object description: The floating IP families currently available for purchase. examples: - ipv4: true ipv6: true properties: ipv4: type: boolean description: The value of `ipv4`. examples: - true ipv6: type: boolean description: The value of `ipv6`. examples: - true required: - ipv4 - ipv6 title: FloatingIpSellableData FloatingIpPricingData: type: object description: What a floating address costs, one price per family. examples: - ipv4: recurring_amount: '3.00' currency: USD billing_cycle: monthly ipv6: recurring_amount: '1.00' currency: USD billing_cycle: monthly properties: ipv4: description: The value of `ipv4`. examples: - recurring_amount: '3.00' currency: USD billing_cycle: monthly anyOf: - $ref: '#/components/schemas/FloatingIpPriceData' - type: 'null' ipv6: description: The value of `ipv6`. examples: - recurring_amount: '1.00' currency: USD billing_cycle: monthly anyOf: - $ref: '#/components/schemas/FloatingIpPriceData' - type: 'null' required: - ipv4 - ipv6 title: FloatingIpPricingData FloatingIpPriceData: type: object description: >- What one family of floating address costs, before a city has been chosen. examples: - recurring_amount: '3.00' currency: USD billing_cycle: monthly properties: recurring_amount: type: string description: The amount charged each billing cycle. examples: - '3.00' currency: type: string description: The three-letter currency code used for monetary amounts. examples: - USD billing_cycle: type: string description: How often the service renews and is billed. examples: - monthly required: - recurring_amount - currency - billing_cycle title: FloatingIpPriceData securitySchemes: http: type: http description: >- Your API key, sent as a bearer token. Create one in the control panel under API Keys, give it only the permissions the integration needs, and copy it when it is created. It cannot be shown again. Each key is restricted to one owned team. The key determines the team for every request. scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.