GetAccounts

API details

Account fields

Filter & sort reference

Use this table when choosing filters[].key and sort.key. It lists every path on Account (and nested objects) and whether the growth-intelligence account list allows it for filtering or sorting (see accountFieldByGraphQLKey in public-api-events). Paths with Filter or Sort set to No are still valid in GraphQL selections (for example acquisition.abuseRuleResult, activation.*) but cannot be used as filters[].key or sort.key until the registry exposes them. Invalid keys produce a GraphQL error.

Input: GetAccountsRequest

All three input fields are optional — omit them to retrieve the first page of all accounts. Combine filters, sort, and pagination to build segmentation queries.

filters · optional · array

An array of filter objects. All filters are ANDed together: an account must satisfy every filter to appear in results. Each filter has three fields:

{
  "key": "<dot-notation field path>",
  "operator": "equals | not_equals | greater_than | less_than | greater_than_or_equal | less_than_or_equal",
  "value": "<string value>"
}

The value is always a string; it is coerced server-side. Use keys from the Account fields table where Filter is Yes. Paths with Filter No are still queryable in GraphQL but cannot be used as filters[].key.

Operators

sort · optional · object

Sort by exactly one field per request. sort.key must be a path whose Sort column is Yes in the Account fields table (same rules as accountFieldByGraphQLKey).

{
  "key": "<dot-notation path — Sort = Yes in Account fields table>",
  "direction": "asc" | "desc"
}

Tip: Sort by monetization.mrr desc to see highest-revenue accounts first, or engagement.activityTrend asc to surface accounts with declining activity. Only paths with Sort = Yes in the Account fields table are valid sort keys.

pagination · optional · object

Cursor-free page-based pagination. Defaults to page 1, size 10 if omitted.

{
  "number": 1,
  "size": 10
}

• number — page number, starts at 1
• size — records per page, max 100

To iterate all results, increment number until the returned account array is empty.

Example request

This example fetches Pro accounts with MRR above $200, ordered by highest MRR first, excluding accounts with a Churned engagement status.

GraphQL query

query GetAccounts($input: GetAccountsRequest!) {
  getAccounts(input: $input) {
    message
    account {
      id
      name
      domain
      source
      createdAt
      acquisition {
        abuseStatus
        touchpointsToSignup
        timeToSignupDays
        initialUtmSource
        abuseRuleResult {
          passed
          ruleId
          ruleName
          description
        }
      }
      monetization {
        plan
        billingStatus
        mrr
        currency
      }
      engagement {
        status
        isActive
        monthlyActiveUsers
        activityTrend
      }
      expansion {
        expansionSignalCount
        contractionSignalCount
      }
    }
  }
}

Variables (JSON)

{
  "input": {
    "filters": [
      {
        "key": "monetization.plan",
        "operator": "equals",
        "value": "pro"
      },
      {
        "key": "engagement.status",
        "operator": "not_equals",
        "value": "Churned"
      },
      {
        "key": "monetization.mrr",
        "operator": "greater_than",
        "value": "200"
      }
    ],
    "sort": {
      "key": "monetization.mrr",
      "direction": "desc"
    },
    "pagination": {
      "number": 1,
      "size": 25
    }
  }
}

cURL

Run this from your terminal to test the API (replace YOUR_API_KEY as needed).

curl --location 'https://api.app.thrivestack.ai/growth-intelligence' \
--header 'content-type: application/json' \
--header 'x-api-key: YOUR_API_KEY' \
--data '
{
  "query": "query GetAccounts($input: GetAccountsRequest!) { getAccounts(input: $input) { message account { id name domain source createdAt acquisition { abuseStatus touchpointsToSignup timeToSignupDays initialUtmSource abuseRuleResult { passed ruleId ruleName description } } monetization { plan billingStatus mrr currency } engagement { status isActive monthlyActiveUsers activityTrend } expansion { expansionSignalCount contractionSignalCount } } } }",
  "variables": {
    "input": {
      "filters": [
        {
          "key": "monetization.plan",
          "operator": "equals",
          "value": "pro"
        },
        {
          "key": "engagement.status",
          "operator": "not_equals",
          "value": "Churned"
        },
        {
          "key": "monetization.mrr",
          "operator": "greater_than",
          "value": "200"
        }
      ],
      "sort": {
        "key": "monetization.mrr",
        "direction": "desc"
      },
      "pagination": {
        "number": 1,
        "size": 25
      }
    }
  }
}
'

Example response

The response wraps matching accounts in data.getAccounts.account[]. The message field is optional in the schema and may be "success" or omitted depending on the server response.

{
  "data": {
    "getAccounts": {
      "message": "success",
      "account": [
        {
          "id": "acc_abc123",
          "name": "Acme Corp",
          "domain": "acme.com",
          "source": ["hubspot", "stripe"],
          "createdAt": "2024-01-15T10:30:00Z",
          "acquisition": {
            "abuseStatus": "clean",
            "touchpointsToSignup": 4,
            "timeToSignupDays": 2,
            "initialUtmSource": "google",
            "abuseRuleResult": [
              { "passed": true, "ruleId": "r_domain", "ruleName": "Domain check", "description": "Domain allowed" }
            ]
          },
          "monetization": {
            "plan": "pro",
            "billingStatus": "active",
            "mrr": 299.0,
            "currency": "USD"
          },
          "engagement": {
            "status": "Healthy",
            "isActive": true,
            "monthlyActiveUsers": 22,
            "activityTrend": 1.32
          },
          "expansion": {
            "expansionSignalCount": 2,
            "contractionSignalCount": 0
          }
        },
        {
          "id": "acc_def456",
          "name": "Globex Inc",
          "domain": "globex.io",
          "source": ["stripe"],
          "createdAt": "2024-02-01T14:00:00Z",
          "acquisition": {
            "abuseStatus": "clean",
            "touchpointsToSignup": 2,
            "timeToSignupDays": 0,
            "initialUtmSource": "direct",
            "abuseRuleResult": []
          },
          "monetization": {
            "plan": "pro",
            "billingStatus": "active",
            "mrr": 249.0,
            "currency": "EUR"
          },
          "engagement": {
            "status": "At Risk",
            "isActive": true,
            "monthlyActiveUsers": 4,
            "activityTrend": 0.61
          },
          "expansion": {
            "expansionSignalCount": 0,
            "contractionSignalCount": 1
          }
        }
      ]
    }
  }
}

Tips & best practices

• Filter values are always strings — the server coerces them to the correct type. Pass "true" for booleans, "299.0" for numbers.
• All filters are ANDed. To segment Pro accounts that are also healthy, add two separate filter objects rather than combining values.
• Registry vs GraphQL. The Account fields table mirrors accountFieldByGraphQLKey for list filters/sort. You can still query response-only paths (for example activation, acquisition.abuseRuleResult) in GraphQL when you need them on the wire.
• Request only the fields you need. Omitting heavy objects like firmographics or acquisition.abuseRuleResult meaningfully reduces response size.
• Use engagement.status for at-risk detection. Values are Healthy, At Risk, Critical, New, and Inactive.
• Expansion signals are additive. Filter on expansion.expansionSignalCount greater_than "0" for upsell candidates, and expansion.contractionSignalCount greater_than "0" for churn risk.