Help Center/ Workspace/ API Reference/ Workspace APIs/ Network/ Verifying Conflicting Network Segments of a Tenant

Updated on 2026-02-10 GMT+08:00

View PDF

Verifying Conflicting Network Segments of a Tenant

Checks whether tenant network segments conflict with each other and returns the list of conflicting network segments.

You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.

POST /v2/{project_id}/check-cidr

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID.

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
tenant_cidrs	No	Array of strings	Tenant network segment.
availability_zone	No	String	AZ used for subscribing to the service.

Status code: 200

**Table 3** Response body parameters
Parameter	Type	Description
manage_cidrs	Array of strings	Planned conflicting network segment.
conflict_cidrs	Array of strings	Overlapped part between tenant network segments and conflicting network segments.

Status code: 400

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
error_detail	String	Error details.
encoded_authorization_message	String	Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 401

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
error_detail	String	Error details.
encoded_authorization_message	String	Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 403

**Table 6** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
error_detail	String	Error details.
encoded_authorization_message	String	Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 404

**Table 7** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
error_detail	String	Error details.
encoded_authorization_message	String	Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

Status code: 500

**Table 8** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error message.
error_detail	String	Error details.
encoded_authorization_message	String	Encrypted detailed reason for rejection. You can call the API decode-authorization-message of STS to decrypt the reason.

GET /v2/29dfe82ada564ac2b927e1ff036d9a9b/checkCidr

{
  "tenant_cidrs" : [ "192.168.0.0/24", "10.0.0.0/16" ]
}

Status code: 200

Conflicting network segments of a tenant.

{
  "manage_cidrs" : [ "215.0.0.0/11" ],
  "conflict_cidrs" : [ "215.128.0.0/11" ]
}

Status Code	Description
200	Conflicting network segments of a tenant.
400	The request cannot be understood by the server due to malformed syntax.
401	Authentication failed.
403	No permissions.
404	Resources not found.
500	An internal service error occurred. For details, see the error code description.