Search cases and users with a manage key

This page covers GET https://prd-api-manage.caseactive.com/v1/<hub id>/search, which finds records in your hub by text. It only ever searches your own hub.

Parameters

• A word in query matches from its start, and allows a typo or two, so jan finds Jane. In Tag IDs, names, email addresses, phone numbers and Reference IDs it also matches anywhere inside, so end-2026 finds rear-end-2026.
• A filter is a field, an operator and a value: := exact, :!= not, and :>, :<, :>= and :<= for numbers. A condition can't contain &&, ||, brackets or commas: send several filter_by parameters instead. A value may hold / and +, such as ref_id:=2026/rear-end or phone:=+15551234567; in an address, send + as %2B, or it arrives as a space.
• Only number fields can sort. Dates in results are Unix seconds.
• A record can take a few minutes to show up after it's created or changed.
• Inquiries can't be searched with a key.

Tables

host_users includes your hub's Virtual AssistantVirtual Assistant An automated team member that posts welcome messages, check-ins and stage posts for the firm; its posts carry a Virtual Assistant badge., whose host_user_type is bot. case_users holds no names: find the person in host_users, then filter case_users by user_id. case_invoices holds published invoices only. Its amounts are in cents, and tax and discount are fractions. A refunded invoice keeps the status paid; its refund is in refund_status.

Examples

A case by its Tag ID:

curl -G https://prd-api-manage.caseactive.com/v1/ca-7e6d5c4b3a2f10/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "table=cases" \
  --data-urlencode "query=*" \
  --data-urlencode "query_by=ref_id" \
  --data-urlencode "filter_by=ref_id:=rear-end-2026"

Active people whose name or email starts with jane, newest first:

curl -G https://prd-api-manage.caseactive.com/v1/ca-7e6d5c4b3a2f10/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "table=host_users" \
  --data-urlencode "query=jane" \
  --data-urlencode "query_by=given_name,family_name,email" \
  --data-urlencode "filter_by=host_user_status:=1" \
  --data-urlencode "sort_by=created_on:desc"

Open cases at one stageStage A step a case moves through, such as Intake or Demand sent, which the firm names and describes and which shows on the case page., using a stage_id from GET /stages: table=cases&query=*&query_by=title&filter_by=case_status:=1&filter_by=case_stage:=stage::20260927120000_8c1f0e2d3b4a59.

Invoices changed since 8 October 2026 at midnight UTC, oldest change first: table=case_invoices&query=*&query_by=name&filter_by=updated_on:>1791417600&sort_by=updated_on:asc.

Results

{
  "data": {
    "found": 1,
    "page": 1,
    "hits": [
      {
        "document": {
          "case_id": "cc-1a2b3c4d5e6f70",
          "host_id": "ca-7e6d5c4b3a2f10",
          "ref_id": "rear-end-2026",
          "title": "Jane Sample auto accident",
          "case_type": "general",
          "case_status": 1,
          "users": ["cu-4f1c2a9e8b7d60", "cu-9d8c7b6a5f4e30"],
          "users_ct": 2,
          "date_opened": 1790899200,
          "created_on": 1790949909,
          "updated_on": 1790949909
        }
      }
    ]
  }
}

found is how many records match. Each hit's document is the record; hits also carry the search engine's own scoring fields, which you can ignore. There's no nextLink: ask for the next page until you've had found results.

A word search can also match similar values, so when you look up one record by an ID, check the document you get back.

If a call is refused