API referenceCount tickets

Tickets

Count tickets

Returns ticket counts for the project's inbox: a per-status breakdown (open, pending, resolved, snoozed, all) and a per-assignment breakdown (all, me, unassigned, assigned). Use it to render status and assignment filter tabs without paging through tickets.

GET

https://api.nabrah.ai/api/ext/omni_v2/ticket/counts

Count tickets

curl --request GET \
  --url 'https://api.nabrah.ai/api/ext/omni_v2/ticket/counts' \
  --header 'X-API-Key: <your-api-key>'

{
  "status_counts": {
    "open": 0,
    "pending": 0,
    "resolved": 0,
    "snoozed": 0,
    "all": 0
  },
  "assignment_counts": {
    "all": 0,
    "me": 0,
    "unassigned": 0,
    "assigned": 0
  }
}

Authentication & scope

Like every Omni v2 ticket endpoint, this is scoped to a single project by your Web API key.

X-API-Key header

Send your Web key (prefix nb_) in the X-API-Key header. The key is bound to exactly one project, so there is no project_id parameter. Validate the key with GET /api/ext/test first.

Response shape

status_counts

Ticket totals per lifecycle status, plus all (the sum across statuses). These drive the status tabs.

openpendingresolvedsnoozedall

assignment_counts

Ticket totals per assignment bucket for the selected status. all is the total for that status; assigned = all - unassigned.

allmeunassignedassigned

Counts are current server-side snapshots and reflect the whole inbox for the given scope, not a single page.

How the two scopes combine

Mirrors a support dashboard's tabs so a badge always matches the list it opens.

status_counts respect assignee_type

Passing assignee_type=me returns per-status counts of only your tickets, matching a status + assignee_type=me listing.

assignment_counts respect status

The assignment breakdown is always computed for the selected status (all statuses when status=all), so you can show every bucket and let the user switch.

Authorization

X-API-Keystringheaderrequired

Your workspace API key. Create one in the dashboard under API keys.

Query parameters

statusenum(open | pending | resolved | snoozed | all)

Lifecycle status the assignment breakdown is computed for.

One of open, pending, resolved, snoozed, or all. Defaults to all. Also selects which status the assignment_counts cover.

assignee_typeenum(all | me | unassigned | assigned)

Assignment bucket the per-status counts are scoped to.

One of all, me, unassigned, or assigned. Defaults to all. Use me to count only the caller's tickets per status, and so on.

Response

200

Successful Response

application/json

422

Validation Error

application/json

API referenceCount tickets

Tickets

Count tickets

GET

https://api.nabrah.ai/api/ext/omni_v2/ticket/counts

Count tickets

curl --request GET \
  --url 'https://api.nabrah.ai/api/ext/omni_v2/ticket/counts' \
  --header 'X-API-Key: <your-api-key>'

{
  "status_counts": {
    "open": 0,
    "pending": 0,
    "resolved": 0,
    "snoozed": 0,
    "all": 0
  },
  "assignment_counts": {
    "all": 0,
    "me": 0,
    "unassigned": 0,
    "assigned": 0
  }
}

Authentication & scope

Like every Omni v2 ticket endpoint, this is scoped to a single project by your Web API key.

X-API-Key header

Send your Web key (prefix nb_) in the X-API-Key header. The key is bound to exactly one project, so there is no project_id parameter. Validate the key with GET /api/ext/test first.

Response shape

status_counts

Ticket totals per lifecycle status, plus all (the sum across statuses). These drive the status tabs.

openpendingresolvedsnoozedall

assignment_counts

Ticket totals per assignment bucket for the selected status. all is the total for that status; assigned = all - unassigned.

allmeunassignedassigned

Counts are current server-side snapshots and reflect the whole inbox for the given scope, not a single page.

How the two scopes combine

Mirrors a support dashboard's tabs so a badge always matches the list it opens.

status_counts respect assignee_type

Passing assignee_type=me returns per-status counts of only your tickets, matching a status + assignee_type=me listing.

assignment_counts respect status

The assignment breakdown is always computed for the selected status (all statuses when status=all), so you can show every bucket and let the user switch.

Authorization

X-API-Keystringheaderrequired

Your workspace API key. Create one in the dashboard under API keys.

Query parameters

statusenum(open | pending | resolved | snoozed | all)

Lifecycle status the assignment breakdown is computed for.

One of open, pending, resolved, snoozed, or all. Defaults to all. Also selects which status the assignment_counts cover.

assignee_typeenum(all | me | unassigned | assigned)

Assignment bucket the per-status counts are scoped to.

One of all, me, unassigned, or assigned. Defaults to all. Use me to count only the caller's tickets per status, and so on.

Response

200

Successful Response

application/json

422

Validation Error

application/json