MeAllowed segments

Allowed segments

Which derivation path segment values are allowed for the user for an action. A UNION across all of the user's allow policies in the Vault: allowed pathIds are extracted from the senderPattern selectors of require rules; a policy without a senderPattern allows everything ("*"). Block policies are ignored, since they'll trigger on the submit itself. Used by the address creation form UI to show only the available variants.

curl -X GET "https://policy-engine-rest.ezig.workers.dev/api/v1/me/allowed-segments?vaultId=example_string&action=create_address" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "action": "create_address",
  "segments": {
    "network": [
      195
    ],
    "app_id": [
      0
    ],
    "asset": "*"
  }
}
GET
/api/v1/me/allowed-segments
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Session token. Mobile/services. The web uses a cookie.

Session token. Mobile/services. The web uses a cookie.
API Key (cookie: session_token)
session_tokenstring
Required

API key (sent in cookie)

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Session token. Mobile/services. The web uses a cookie.

path
parameterstring
Required

API Key for authentication. Provide your API key in the cookie.

Query Parameters

actionstring
Required
Example:
create_address

Responses

actionstring
Required
segmentsobject
Required

Segment code → allowed pathIds or "*" (no restrictions). An empty object means there are no allow policies