Formo Alerts API

openapi: 3.2.0
info:
  title: Formo Public Alerts API
  description: 'REST API for managing Formo projects, analytics, alerts, boards, charts, contracts, segments, and AI chat.


    **Auth.** Every endpoint on `api.formo.so` requires a workspace API key with the appropriate scopes (see `x-api-scopes`). The one exception is `POST /v0/raw_events`, which runs on `events.formo.so` and authenticates with the project SDK write key instead.


    **Response shape.** Successful responses return the resource directly (or `{ data: [...], total, page, size, has_more }` for paginated lists). HTTP status carries success/failure; there is no envelope wrapping success bodies.


    **Errors.** Non-2xx responses from `api.formo.so` use the `Error` envelope, with two exceptions: some rate-limit rejections reply in plain text, and `POST /v0/raw_events` returns a plain `{ "error": "..." }` object. Treat the HTTP status as authoritative and parse defensively: `{ error: { code, message, doc_url, param?, details? } }`. Branch on the machine-readable `code` (see `ErrorCode` enum) and follow `doc_url` to the matching section of the errors reference.


    **Idempotency.** Pass an `Idempotency-Key` header on write requests to alerts, boards, charts, contracts, segments, and import to make retries safe; the response is cached for 24 h and replayed on duplicate keys. Profile writes and `POST /v0/query` do not support it.'
  version: 0.1.0
  contact:
    name: Formo
    url: https://formo.so
servers:
- url: https://api.formo.so
  description: API Server (boards, alerts, contracts, segments, profiles, query, import)
- url: https://events.formo.so
  description: Events Server (event ingestion)
security:
- WorkspaceApiKey: []
tags:
- name: Alerts
  description: Manage project alerts and notifications
paths:
  /v0/alerts:
    get:
      operationId: listAlerts
      summary: List alerts
      description: 'List alerts for the project scoped to the API key. Paginated: see `page` and `size` query params; the response carries `total` and `has_more` so callers can walk pages.'
      tags:
      - Alerts
      x-required-scope: alerts:read
      parameters:
      - $ref: '#/components/parameters/Page'
      - $ref: '#/components/parameters/Size'
      responses:
        '200':
          description: Paginated list of alerts
          content:
            application/json:
              schema:
                allOf:
                - $ref: '#/components/schemas/PaginatedListMeta'
                - type: object
                  required:
                  - data
                  properties:
                    data:
                      type: array
                      items:
                        $ref: '#/components/schemas/Alert'
              example:
                data:
                - id: alrt_4f8e2c1a9b3d4e5f
                  project_id: proj_abc123
                  name: Daily revenue drop
                  trigger_type: event
                  status: active
                  trigger_filters:
                  - value: transaction
                    field: event
                    op: eq
                  - value: '1000'
                    numericThreshold: sum
                    field: revenue
                    op: lt
                  recipient:
                  - type: email
                    value:
                    - alerts@myapp.com
                  - type: slack
                    value:
                    - C0123456789
                  has_secret: false
                  created_at: '2026-04-12T09:32:18.000Z'
                  updated_at: '2026-04-25T14:01:55.000Z'
                page: 1
                size: 100
                total: 1
                has_more: false
    post:
      operationId: createAlert
      summary: Create alert
      description: Create a new alert for the project.
      tags:
      - Alerts
      x-required-scope: alerts:write
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
                  minLength: 1
                trigger_type:
                  type: string
                  enum:
                  - event
                  - user
                trigger_filters:
                  type: array
                  items:
                    $ref: '#/components/schemas/AlertFilter'
                recipient:
                  type: array
                  items:
                    type: object
                    properties:
                      type:
                        type: string
                        enum:
                        - email
                        - slack
                        - webhook
                      value:
                        type: array
                        items:
                          type: string
                secret:
                  type: string
                  description: Webhook signing secret
              required:
              - name
              - trigger_type
              - trigger_filters
            examples:
              eventAlertWithWebhook:
                summary: Alert on swap events from mobile devices with webhook
                value:
                  name: Mobile swap alert
                  trigger_type: event
                  trigger_filters:
                  - value: swap
                    field: type
                    op: eq
                  - value: mobile
                    field: device
                    op: eq
                  - value: '1000'
                    numericThreshold: '1000'
                    field: volume
                    op: gt
                  recipient:
                  - type: webhook
                    value:
                    - https://hooks.myapp.com/formo-alerts
                  - type: email
                    value:
                    - alerts@myapp.com
                  secret: whsec_mysigningsecret123
              eventAlertWithUtmFilter:
                summary: Alert on events from specific UTM campaigns
                value:
                  name: Paid campaign activity
                  trigger_type: event
                  trigger_filters:
                  - value: purchase
                    field: type
                  - value: google
                    field: utm_source
                    op: eq
                  - value: cpc
                    field: utm_medium
                    op: eq
                  recipient:
                  - type: slack
                    value:
                    - '#marketing-alerts|https://hooks.slack.com/services/REDACTED'
              userAlertWithLocationFilter:
                summary: Alert when new users spike from a specific country
                value:
                  name: US user spike
                  trigger_type: user
                  trigger_filters:
                  - value: US
                    field: location
                    op: eq
                  - value: '10000'
                    numericThreshold: '10000'
                    field: net_worth_usd
                    op: gte
                  recipient:
                  - type: email
                    value:
                    - team@myapp.com
              eventAlertWithNumericThreshold:
                summary: Alert when users hold >5 tokens in a specific app
                value:
                  name: High token holder alert
                  trigger_type: event
                  trigger_filters:
                  - value: uniswap
                    numericThreshold: '5'
                    field: apps
                    op: gt
                  - value: '1'
                    numericThreshold: '3'
                    field: chains
                    op: gte
                  recipient:
                  - type: webhook
                    value:
                    - https://hooks.myapp.com/token-alerts
      responses:
        '201':
          description: Alert created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Alert'
        '400':
          $ref: '#/components/responses/BadRequest'
        '409':
          $ref: '#/components/responses/Conflict'
      parameters:
      - $ref: '#/components/parameters/IdempotencyKey'
  /v0/alerts/{alertId}:
    get:
      operationId: getAlert
      summary: Get alert
      tags:
      - Alerts
      parameters:
      - name: alertId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Alert details
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Alert'
              example:
                id: alrt_4f8e2c1a9b3d4e5f
                project_id: proj_abc123
                name: Daily revenue drop
                trigger_type: event
                status: active
                trigger_filters:
                - value: transaction
                  field: event
                  op: eq
                - value: '1000'
                  numericThreshold: sum
                  field: revenue
                  op: lt
                recipient:
                - type: email
                  value:
                  - alerts@myapp.com
                - type: slack
                  value:
                  - C0123456789
                has_secret: false
                created_at: '2026-04-12T09:32:18.000Z'
                updated_at: '2026-04-25T14:01:55.000Z'
        '404':
          $ref: '#/components/responses/NotFound'
      x-required-scope: alerts:read
    put:
      operationId: updateAlert
      summary: Update alert
      tags:
      - Alerts
      parameters:
      - name: alertId
        in: path
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/IdempotencyKey'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
                  minLength: 1
                trigger_type:
                  type: string
                  enum:
                  - event
                  - user
                trigger_filters:
                  type: array
                  items:
                    $ref: '#/components/schemas/AlertFilter'
                recipient:
                  type: array
                  items:
                    type: object
                secret:
                  type: string
              required:
              - name
              - trigger_type
              - trigger_filters
            examples:
              updateRecipients:
                summary: Update alert recipients
                value:
                  name: Mobile swap alert (updated)
                  trigger_type: event
                  trigger_filters:
                  - value: swap
                    field: type
                  - value: mobile
                    field: device
                  recipient:
                  - type: webhook
                    value:
                    - https://hooks.myapp.com/v2/alerts
                  - type: slack
                    value:
                    - '#alerts|https://hooks.slack.com/services/REDACTED'
      responses:
        '200':
          description: Alert updated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Alert'
        '400':
          $ref: '#/components/responses/BadRequest'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/Conflict'
      x-required-scope: alerts:write
    delete:
      operationId: deleteAlert
      summary: Delete alert
      tags:
      - Alerts
      parameters:
      - name: alertId
        in: path
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/IdempotencyKey'
      responses:
        '200':
          description: Alert deleted
          content:
            application/json:
              schema:
                type: number
        '400':
          $ref: '#/components/responses/BadRequest'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/Conflict'
      x-required-scope: alerts:write
    patch:
      operationId: toggleAlertStatus
      summary: Toggle alert status
      tags:
      - Alerts
      parameters:
      - name: alertId
        in: path
        required: true
        schema:
          type: string
      - $ref: '#/components/parameters/IdempotencyKey'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                status:
                  type: string
                  enum:
                  - active
                  - inactive
              required:
              - status
            examples:
              activate:
                summary: Activate alert
                value:
                  status: active
              deactivate:
                summary: Deactivate alert
                value:
                  status: inactive
      responses:
        '200':
          description: Alert status updated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Alert'
        '400':
          $ref: '#/components/responses/BadRequest'
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          $ref: '#/components/responses/Conflict'
      x-required-scope: alerts:write
components:
  schemas:
    Error:
      type: object
      description: Standard error envelope returned by every public API endpoint for any non-2xx response. The HTTP status code carries success/failure; the body provides a machine-readable `code`, a human-readable `message`, and a `doc_url` pointing at the matching section of the docs so agents can fetch context on the fly.
      properties:
        error:
          type: object
          required:
          - code
          - message
          - doc_url
          properties:
            code:
              $ref: '#/components/schemas/ErrorCode'
            message:
              type: string
              description: Human-readable error description. Wording may change between releases, so branch on `code`, not `message`.
            doc_url:
              type: string
              format: uri
              description: Link to the matching section of the errors reference at https://docs.formo.so/api/errors.
            param:
              type: string
              description: When the error pertains to a specific request field, the dotted path to that field (e.g. `body.trigger_filters.0.value`).
            details:
              type: object
              additionalProperties: true
              description: 'Code-specific extra context. For `INVALID_VALIDATION_REQUEST` this is a `{ fieldPath: message }` map of every Zod validation failure.'
      required:
      - error
    AlertFilter:
      type: object
      description: A project-alert trigger filter using the canonical envelope.
      properties:
        field:
          type: string
          description: Column or property targeted by this filter.
        op:
          type: string
          enum:
          - eq
          - neq
          - gt
          - lt
          - gte
          - lte
          - in
          - nin
          - startsWith
          - endsWith
          - contains
          - notEmpty
          - isEmpty
          description: Canonical comparison operator token.
        value:
          type: string
        numericThreshold:
          type: string
      required:
      - field
      - op
      - value
    ErrorCode:
      type: string
      description: Stable, enumerated error codes. New codes may be added in any release; clients should treat unknown codes as the closest matching HTTP status family.
      enum:
      - INTERNAL_SERVER_ERROR
      - INVALID_VALIDATION_REQUEST
      - UNAUTHORIZED
      - BAD_REQUEST
      - FORBIDDEN
      - NOT_FOUND
      - CONFLICT
      - INVALID_CHAIN_ID
      - CONTEXT_LIMIT_EXCEEDED
      - SERVICE_UNAVAILABLE
      - TOO_MANY_REQUESTS
      - IDEMPOTENCY_IN_PROGRESS
      - INVALID_IDEMPOTENCY_KEY
    Alert:
      type: object
      properties:
        id:
          type: string
        name:
          type: string
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
          nullable: true
        trigger_type:
          type: string
          enum:
          - event
          - user
        status:
          type: string
          enum:
          - active
          - inactive
        trigger_filters:
          type: array
          items:
            $ref: '#/components/schemas/AlertFilter'
        recipient:
          type: array
          items:
            type: object
            properties:
              type:
                type: string
                enum:
                - email
                - slack
                - webhook
              value:
                type: array
                items:
                  type: string
            required:
            - type
            - value
        project_id:
          type: string
        has_secret:
          type: boolean
      required:
      - id
      - name
      - trigger_type
      - status
      - project_id
    PaginatedListMeta:
      type: object
      description: 'Pagination cursor returned alongside `data` on every paginated list endpoint. Use these to walk pages: `has_more` is true while `page * size < total`. Combine with the matching `Page` and `Size` query parameters to request the next page.'
      required:
      - page
      - size
      - total
      - has_more
      properties:
        page:
          type: integer
          description: 1-indexed page number echoed from the request.
        size:
          type: integer
          description: Page size echoed from the request.
        total:
          type: integer
          description: Total row count across all pages.
        has_more:
          type: boolean
          description: True when more pages remain (`page * size < total`).
  parameters:
    Size:
      name: size
      in: query
      required: false
      schema:
        type: integer
        minimum: 1
        maximum: 200
        default: 100
      description: Page size. Defaults to 100, capped at 200.
    Page:
      name: page
      in: query
      required: false
      schema:
        type: integer
        minimum: 1
        default: 1
      description: 1-indexed page number. Defaults to 1.
    IdempotencyKey:
      name: Idempotency-Key
      in: header
      required: false
      schema:
        type: string
        maxLength: 255
      description: Optional unique value (e.g. a UUID v4) that lets you safely retry POST/PUT/PATCH/DELETE requests. The first request runs normally; subsequent requests with the same key replay the stored response (status + body) for 24 hours, so retries can never double-create or double-charge. Two concurrent requests with the same key return `409 IDEMPOTENCY_IN_PROGRESS`. Generate a fresh key per logical operation.
  responses:
    BadRequest:
      description: 'The request was rejected. `code` is either `INVALID_VALIDATION_REQUEST` (Zod schema mismatch; `details` carries a `{ fieldPath: message }` map) or `BAD_REQUEST` (semantic validation failure outside Zod, e.g. mismatched IDs, business-rule violations). Branch on `code`, not status, to tell the two apart.'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          examples:
            validation:
              summary: Zod schema mismatch
              value:
                error:
                  code: INVALID_VALIDATION_REQUEST
                  message: Invalid request data
                  doc_url: https://docs.formo.so/api/errors#invalid_validation_request
                  details:
                    body.name: String must contain at least 1 character(s)
            semantic:
              summary: Semantic validation failure
              value:
                error:
                  code: BAD_REQUEST
                  message: Target board must be different from the current board
                  doc_url: https://docs.formo.so/api/errors#bad_request
    Conflict:
      description: The request conflicts with current resource state, or an `Idempotency-Key` request with the same key is currently in flight.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: IDEMPOTENCY_IN_PROGRESS
              message: A request with this Idempotency-Key is already in progress. Retry shortly.
              doc_url: https://docs.formo.so/api/errors#idempotency_in_progress
    NotFound:
      description: The requested resource does not exist or is not visible to this API key's workspace.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: NOT_FOUND
              message: Alert not found
              doc_url: https://docs.formo.so/api/errors#not_found
  securitySchemes:
    WorkspaceApiKey:
      type: http
      scheme: bearer
      description: Workspace API key (e.g. `formo_xxx`). Create one in the Formo dashboard under Team Settings > API.
    X402Payment:
      type: apiKey
      in: header
      name: X-PAYMENT
      description: x402 payment payload generated after the gateway returns a 402 challenge.
    MPPPayment:
      type: apiKey
      in: header
      name: Authorization
      description: MPP payment authorization header, formatted as `Payment <payload>`, generated after the gateway returns a 402 challenge.
    SdkWriteKey:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 'Project SDK write key (a JWT), sent as `Authorization: Bearer <write key>`. This is NOT the `formo_...` workspace API key used on api.formo.so. Find it in the Formo dashboard under the project’s settings.'
x-api-scopes:
  description: API key scopes control access to endpoints. Create keys with the required scopes in Team Settings > API.
  scopes:
    alerts:read: List and get alerts
    alerts:write: Create, update, delete alerts (requires alerts:read)
    boards:read: List and get boards and charts
    boards:write: Create, update, delete boards and charts (requires boards:read)
    contracts:read: List contracts
    contracts:write: Create, update, delete contracts (requires contracts:read)
    segments:read: List segments
    segments:write: Create and delete segments (requires segments:read)
    profiles:read: Search and get wallet profiles
    profiles:write: Update wallet properties, manage labels, and import addresses (requires profiles:read)
    query:read: Execute SQL analytics queries and read pre-built analytics endpoints (KPIs, top pages, lifecycle, retention, revenue, etc.)