PATCH Zones

Use this endpoint to update existing zones.

User level: Advanced

Endpoint

PATCH /v1/{scopeId}/zones/{id}

Update rules

• The API validates server-side whether the record belongs to the allowed organization and branch.
• This is a branch-or-null resource, but the PATCH call still uses a branch UUID in {scopeId}.
• Only explicitly allowed fields can be updated.
• Unknown or disallowed fields return 400 invalid_update.

Allowed update fields

Example request

curl -X PATCH "https://api.routix.com/v1/550e8400-e29b-41d4-a716-446655440000/zones/3c312fd9-975e-43d8-a661-75d5649b1d8d" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIs..." \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Zone A",
    "postal_code_to": "1999"
  }'

Example response

{
  "data": {
    "id": "3c312fd9-975e-43d8-a661-75d5649b1d8d",
    "name": "Zone A",
    "postal_code_from": "1000",
    "postal_code_to": "1999",
    "country_id_master_data": "NL"
  },
  "version": "v1"
}

Error response

{
  "error": "invalid_update",
  "error_description": "One or more fields are not allowed for updates on zones"
}

Possible error codes

• 400 invalid_request
• 400 invalid_update
• 401 unauthorized
• 401 invalid_token
• 403 invalid_token_type
• 403 insufficient_scope
• 404 not_found
• 405 method_not_allowed

Related pages

• Zones GET
• API calls & examples
• Setup guide