Associate an IPv4 address with a network interface
On an interface not running on a host the association completes at once; otherwise association.state is associating until the host confirms. Refused with 409 interface_deleting while the address's current network interface is being deleted, and 409 association_in_progress while its association is still changing. On a private network interface the address is mapped 1:1 onto its primary private IPv4 (the guest sees only the private address); its VPC needs an attached network gateway (409 vpc_has_no_gateway), and a host it's bound on must support the gateway (409 host_unsupported) and have a prefix for it (409 host_prefix_limit).
https://network-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/ipv4-addresses/{ipv4Address}/associateAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
200
The address.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.