Create Ip Rule

POST /ip-rules

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — IpRuleCreate

Field	Type		Notes
cidr	string	required	min length 1 max length 64
action	allow | deny	required	—
description	string | null	optional	max length 300
scope	workspace | organization | platform	optional	Default "workspace".

Responses

Status	Description	Body
201	Successful Response	IpRuleView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/ip-rules \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "cidr": "string",
       "action": "allow"
     }'

Response — IpRuleView

Field	Type		Notes
id	string (uuid)	required	—
cidr	string	required	—
action	allow | deny	required	—
description	string | null	optional	—
is_active	boolean	required	—
scope	workspace | organization | platform	required	—
organization_id	string (uuid) | null	optional	—
workspace_id	string (uuid) | null	optional	—
created_at	string (date-time)	required	—