Assign a delegated prefix to a network interface
An IPv4 /28 or IPv6 /80 from the interface's own subnet, for addresses the instance routes itself: the prefix given, or a free aligned one. The operation's address holds the prefix in CIDR form, and it succeeds once the interface's host is programmed. Requires an Idempotency-Key (1–200 characters); a retry with it answers the same operation as it is now. 400 invalid_request for a wrong length, a prefix not aligned or outside the subnet, or one overlapping a subnet's reserved addresses. Refused with 409 public_interface, interface_not_available, migration_in_progress, host_unsupported and private_address_limit_exceeded (at most 16 IPv4 and 2 IPv6 prefixes per interface; a VPC's addresses, prefixes and interfaces total at most 5,000); 409 address_in_use for a prefix overlapping any address, prefix or VIP, and 409 prefix_unavailable when no aligned block is free.
https://network-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/network-interfaces/{networkInterface}/private-prefixes/assignAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
202
Accepted: the operation (also at Location; poll it after Retry-After, 2 seconds), even when it completes at once.
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.