SuperOps.ai API Patterns

Overview

SuperOps.ai uses a GraphQL API for all integrations. Unlike REST APIs, GraphQL allows you to request exactly the data you need in a single request. This skill covers authentication, query patterns, mutations, pagination, rate limiting, and error handling.

Authentication

SuperOps.ai uses Bearer token authentication plus a subdomain header. You need:

1. API Token - Generated from your profile settings
2. Customer Subdomain - Your SuperOps.ai subdomain

Required Headers

POST /msp
Content-Type: application/json
Authorization: Bearer YOUR_API_TOKEN
CustomerSubDomain: yourcompany

The CustomerSubDomain header is non-standard and mandatory — omitting it returns an authentication failure even with a valid token.

Generating an API Token

1. Log in to SuperOps.ai
2. Click settings icon > "My Profile"
3. Navigate to "API token" tab
4. Click "Generate token"
5. Copy and securely store the token

Note: You can only have one active API token. Regenerating creates a new token and invalidates the old one.

Environment Variables

export SUPEROPS_API_KEY="your-api-token"
export SUPEROPS_SUBDOMAIN="yourcompany"
export SUPEROPS_REGION="us"  # or "eu"

API Endpoints

Endpoints are region-specific; using the wrong region fails auth rather than redirecting.

GraphQL Request Format

Basic Structure

{
  "query": "query or mutation string",
  "variables": {
    "variableName": "value"
  }
}

Nearly every list query takes a single input argument of type ListInfoInput!, and mutations take a single input of a per-entity input type.

Query Example

query getClientList($input: ListInfoInput!) {
  getClientList(input: $input) {
    clients {
      accountId
      name
      status
    }
    listInfo {
      totalCount
      hasNextPage
      endCursor
    }
  }
}

Variables:

{
  "input": {
    "first": 50,
    "filter": {
      "status": "Active"
    }
  }
}

Mutation Example

mutation createTicket($input: CreateTicketInput!) {
  createTicket(input: $input) {
    ticketId
    ticketNumber
    subject
    status
  }
}

Variables:

{
  "input": {
    "subject": "Issue with email",
    "client": {
      "accountId": "client-uuid"
    },
    "priority": "HIGH"
  }
}

Cursor-Based Pagination

Pagination Parameters

Pagination Pattern

Every list result carries a listInfo object with totalCount, hasNextPage, hasPreviousPage, startCursor, and endCursor (see references/examples.md for a full response body).

Request listInfo { hasNextPage endCursor }, then pass endCursor as after on the next call. Loop while hasNextPage is true.

First page:

{
  "input": {
    "first": 100
  }
}

Next page:

{
  "input": {
    "first": 100,
    "after": "YXJyYXljb25uZWN0aW9uOjk5"
  }
}

See references/examples.md for a complete fetch-all-pages implementation.

Rate Limiting

• Limit: 800 requests per minute
• Scope: Per API token
• Reset: Rolling 60-second window

Rate Limit Headers

X-RateLimit-Limit: 800
X-RateLimit-Remaining: 742
X-RateLimit-Reset: 1708012345

Rate Limit Response (HTTP 429)

{
  "errors": [
    {
      "message": "Rate limit exceeded. Please retry after 30 seconds.",
      "extensions": {
        "code": "RATE_LIMITED",
        "retryAfter": 30
      }
    }
  ]
}

Honor extensions.retryAfter and add jitter. See references/examples.md for a retry-with-backoff implementation.

Query Filtering

Filter Operators

Equality is implicit — { "status": "Active" } is the eq form; a bare array is the in form.

Complex Filter Example

{
  "input": {
    "filter": {
      "and": [
        { "status": ["Open", "In Progress"] },
        { "priority": { "in": ["Critical", "High"] } },
        {
          "or": [
            { "client": { "accountId": "client-1" } },
            { "client": { "accountId": "client-2" } }
          ]
        }
      ]
    }
  }
}

Ordering Results

{
  "input": {
    "orderBy": {
      "field": "createdTime",
      "direction": "DESC"
    }
  }
}

Date/Time Handling

All dates and times must be in UTC with ISO 8601 format:

2024-02-15T10:30:00Z

Date Range Queries

{
  "filter": {
    "createdTime": {
      "gte": "2024-02-01T00:00:00Z",
      "lte": "2024-02-29T23:59:59Z"
    }
  }
}

Error Handling

Errors return HTTP 200

GraphQL errors arrive in an errors array with data: null — check response.errors rather than relying on the HTTP status.

{
  "data": null,
  "errors": [
    {
      "message": "Client not found",
      "locations": [{ "line": 2, "column": 3 }],
      "path": ["getClient"],
      "extensions": {
        "code": "NOT_FOUND",
        "field": "accountId"
      }
    }
  ]
}

See references/examples.md for an error-dispatch wrapper.

Null resets a field

• Empty values are represented as null
• Passing null as input can reset a field
• Use undefined (don't include field) to leave unchanged

// This will CLEAR the assignee
{ "assignee": null }

// This will leave assignee unchanged
{ /* assignee field omitted */ }

Request Best Practices

1. Request only needed fields - GraphQL returns exactly what you ask for; over-selecting costs latency
2. Use variables - Reusable queries and no injection of raw values into query strings
3. Batch related queries - One request with aliases beats several round-trips against the rate limit
4. Cache reference data - Client and technician lists change rarely; a short TTL cache saves quota

See references/examples.md for worked good/avoid examples of each and a complete GraphQL client implementation.

Related Skills

• SuperOps.ai Tickets - Ticket operations
• SuperOps.ai Assets - Asset queries
• SuperOps.ai Clients - Client management
• SuperOps.ai Alerts - Alert operations
• SuperOps.ai Runbooks - Script execution