Skip to main content
POST
/
v1
/
networks
/
policies
/
querying
Create a querying policy for a (product, network) pair.
curl --request POST \
  --url https://api.example.com/v1/networks/policies/querying \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "product_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "network_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "name": "<string>"
}
'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "network_product_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "entity_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "name": "<string>",
  "is_default": true
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Body of POST /networks/policies/querying.

The dialog presents two independent dropdowns — Product and Network — so the REST contract carries those ids directly. The backend resolves (or auto-creates) the join NetworkProduct row and creates the policy via the repo layer in a single GraphQL mutation.

Per-model / per-field selections are authored separately via the wizard's PUT /networks/policies/querying/{policy_id}/configuration route, so this payload intentionally has no nested models list.

​
product_id
string<uuid>
required
​
network_id
string<uuid>
required
​
name
string
required

Response

Successful Response

​
id
string<uuid>
required
​
network_product_id
string<uuid>
required
​
entity_id
string<uuid>
required
​
name
string
required
​
is_default
boolean
required