Skip to main content

Update Connector Priority

Set a connector's development priority on the roadmap.

PATCH /api/connectors/{id}/priority

note

Priority is metadata, not forensic content, so this does not create a new connector version. It mutates the connector in place, records the editing analyst as updatedById, and writes an audit-log entry.

Authorization​

  • Analyst (or admin) with an analyst profile. Unauthenticated requests receive 401; users without the role/profile receive 403.

Path Parameters​

ParameterTypeRequiredDescription
idstringYesConnector ID

Request Body​

FieldTypeRequiredDescription
prioritystringYesOne of low, medium, high, critical
{ "priority": "high" }

Response​

{ "priority": "high" }

Example Request​

curl -X PATCH "https://api.traces.io/api/connectors/conn_slack001/priority" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{ "priority": "critical" }'

Error Responses​

400 Bad Request​

The priority value is missing or invalid:

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "priority must be one of: low, medium, high, critical"
  }
}

401 Unauthorized​

{ "error": { "code": "UNAUTHORIZED", "message": "Authentication required" } }

403 Forbidden​

{ "error": { "code": "FORBIDDEN", "message": "Analyst role required" } }

404 Not Found​

{ "error": { "code": "NOT_FOUND", "message": "Connector not found" } }

500 Internal Server Error​

{ "error": { "code": "INTERNAL_ERROR", "message": "Failed to update priority" } }