Anomalo

Anomalo Lineage API

The Lineage API from Anomalo — 3 operation(s) for lineage.

Documentation GitHub OpenAPI

Operations 4

POST /table_lineage_edge Add table lineage edge #

DELETE /table_lineage_edge Remove table lineage edge #

GET /tables/{table_id}/lineage/downstream List table downstream lineage #

GET /tables/{table_id}/lineage/upstream List table upstream lineage #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/anomalo:anomalo-lineage-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Anomalo Public Lineage API
  version: v1
  summary: Data quality monitoring, table configuration and check orchestration for the Anomalo platform.
  description: 'The Anomalo Public API (`/api/public/v1/`) drives Anomalo''s data quality monitoring platform: connect and refresh warehouses, configure which tables are monitored, create and run data quality checks, read check-run results and table data profiles, manage table/check labels, administer users, API keys and access groups, record table lineage edges, and manage notification channels.'
  contact:
    name: Anomalo
    url: https://www.anomalo.com/contact-us/
  license:
    name: Apache-2.0
    identifier: Apache-2.0
  x-derived-from: https://pypi.org/project/anomalo/0.46.0/
  x-derived-by: API Evangelist enrichment pipeline
  x-unofficial: true
servers:
- url: https://{instance}/api/public/v1
  description: Anomalo is deployed per-tenant. The client reads the host from the `ANOMALO_INSTANCE_HOST` environment variable.
  variables:
    instance:
      default: app.anomalo.com
      description: Your Anomalo instance host, e.g. app.anomalo.com or my-company.anomalo.com
security:
- AnomaloToken: []
tags:
- name: Lineage
paths:
  /table_lineage_edge:
    post:
      operationId: add_table_lineage_edge
      summary: Add table lineage edge
      tags:
      - Lineage
      x-client-methods:
      - add_table_lineage_edge
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                source: {}
                destination: {}
              additionalProperties: false
      responses:
        '200':
          description: Successful response. The client returns the decoded JSON body.
          content:
            application/json:
              schema:
                type: object
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/ServerError'
    delete:
      operationId: remove_table_lineage_edge
      summary: Remove table lineage edge
      tags:
      - Lineage
      x-client-methods:
      - remove_table_lineage_edge
      parameters:
      - name: source_table_id
        in: query
        required: false
        schema:
          type: integer
      - name: source_external_ref
        in: query
        required: false
        schema: {}
      - name: destination_table_id
        in: query
        required: false
        schema:
          type: integer
      - name: destination_external_ref
        in: query
        required: false
        schema: {}
      responses:
        '200':
          description: Successful response. The client returns the decoded JSON body.
          content:
            application/json:
              schema:
                type: object
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/ServerError'
  /tables/{table_id}/lineage/downstream:
    get:
      operationId: list_table_downstream_lineage
      summary: List table downstream lineage
      tags:
      - Lineage
      x-client-methods:
      - list_table_downstream_lineage
      parameters:
      - name: table_id
        in: path
        required: true
        description: Path identifier `table_id`.
        schema:
          type: integer
      - name: limit
        in: query
        required: false
        schema: {}
      - name: offset
        in: query
        required: false
        schema: {}
      - name: max_hops
        in: query
        required: false
        schema: {}
      responses:
        '200':
          description: Successful response. The client returns the decoded JSON body.
          content:
            application/json:
              schema:
                type: object
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/ServerError'
  /tables/{table_id}/lineage/upstream:
    get:
      operationId: list_table_upstream_lineage
      summary: List table upstream lineage
      tags:
      - Lineage
      x-client-methods:
      - list_table_upstream_lineage
      parameters:
      - name: table_id
        in: path
        required: true
        description: Path identifier `table_id`.
        schema:
          type: integer
      - name: limit
        in: query
        required: false
        schema: {}
      - name: offset
        in: query
        required: false
        schema: {}
      - name: max_hops
        in: query
        required: false
        schema: {}
      responses:
        '200':
          description: Successful response. The client returns the decoded JSON body.
          content:
            application/json:
              schema:
                type: object
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/ServerError'
components:
  responses:
    BadRequest:
      description: Bad request. Raised by the client as BadRequestException (not retried).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Forbidden:
      description: Authenticated but not permitted for the active organization or resource.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Missing or invalid API token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: Resource not found.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ServerError:
      description: Server error. The first-party client retries these up to 5 times with exponential jitter backoff.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      description: Error body. The first-party client raises BadRequestException for 4xx and RuntimeError for 5xx, carrying the raw response text; Anomalo does not publish a documented error envelope schema.
      additionalProperties: true
  securitySchemes:
    AnomaloToken:
      type: apiKey
      in: header
      name: X-Anomalo-Token
      description: Anomalo API secret token. The first-party client sends it as `X-Anomalo-Token` by default (`legacy_auth=True`), read from the `ANOMALO_API_SECRET_TOKEN` environment variable.
    BearerToken:
      type: http
      scheme: bearer
      description: 'Anomalo API secret token sent as `Authorization: Bearer <token>`. Selected in the first-party client with `legacy_auth=False`.'