Shipeasy
APIOperations

List tag automation rules

The project's tag automation rules in evaluation order. Each rule matches newly filed queue items by tag (or ticket type) and applies its actions — assign a…

The project's tag automation rules in evaluation order. Each rule matches newly filed queue items by tag (or ticket type) and applies its actions — assign a person, launch a connected coding agent, set status or priority, subscribe emails.

Use case

Check what automation already exists before adding a rule, so a new one doesn't duplicate or shadow it.

GET
/api/admin/ops/routing-rules

Authorization

bearerSdkKey
AuthorizationBearer <token>

Pass an admin SDK key as Authorization: Bearer sdk_admin_…. Mint via POST /api/admin/keys with type: "admin".

In: header

Header Parameters

X-Project-Id?string

Project the request operates on. Optional — defaults to the project the SDK key belongs to; pass it only to scope a multi-project key (the generated client sets it once from its configuration, so per-call callers never thread it).

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://shipeasy.ai/api/admin/ops/routing-rules"
[
  {
    "tags": [
      "string"
    ],
    "types": [
      "error"
    ],
    "enabled": true,
    "user": "string",
    "connector": "string",
    "agentPrompt": "string",
    "status": "open",
    "priority": "nice_to_have",
    "subscribers": [
      "user@example.com"
    ],
    "skipApproval": true,
    "triage": true,
    "triageAgent": "string",
    "triageAutoApprove": true
  }
]
{
  "error": "Malformed request (bad JSON, missing project scope).",
  "code": "BAD_REQUEST"
}
{
  "error": "Missing or invalid admin SDK key.",
  "code": "UNAUTHORIZED"
}

{
  "error": "Key is valid but not allowed to act on this project.",
  "code": "FORBIDDEN"
}

Was this page helpful?