How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bigeye Lineage Service API

The LineageService API from Bigeye — 8 operation(s) for lineageservice.

Bigeye Lineage Service API is one of 45 APIs that Bigeye publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include LineageService. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 11 operations across 8 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version version not set.

Requests are made against a single base URL, https://app.bigeye.com.

11 operations 8 paths 16 schemas 3 DELETE3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
version not set
Base URL
https://app.bigeye.com
Authentication
HTTP Basic, API Key, API Key
Resource Areas
1

Authentication & Security 3

Bigeye Lineage Service API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as Authorization (Agent_API_Key). An API key is passed in the header as Authorization (Personal_API_Key). By default, every request must be authenticated.

  • Agent_API_Key — Add 'apikey ' to the beginning of your api key
  • Personal_API_Key — Add 'apikey ' to the beginning of your api key

Paths & Operations 11

Across 8 paths, the API surfaces 11 operations — 3 DELETE, 3 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

LineageService 11
POST
/api/v1/lineage/nodes
Create a custom node
LineageService_CreateDataNode body → 200default
POST
/api/v1/lineage/relationships
Create a custom edge between two nodes
LineageService_CreateLineageRelationship body → 200default
DELETE
/api/v1/lineage/nodes/{dataNodeId}
Delete a node by ID
LineageService_DeleteDataNode 1 param → 200default
GET
/api/v1/lineage/nodes/{dataNodeId}
Get a node by ID
LineageService_GetDataNode 1 param → 200default
POST
/api/v1/lineage/nodes/{dataNodeId}/downstream/fetch
Get downstream nodes for a given node
LineageService_GetDownstreamDataNodes 1 param body → 200default
DELETE
/api/v1/lineage/relationships/{lineageRelationshipId}
Delete an edge by ID
LineageService_DeleteLineageRelationship 1 param → 200default
GET
/api/v1/lineage/relationships/{lineageRelationshipId}
Get an edge by ID
LineageService_GetLineageRelationship 1 param → 200default
DELETE
/api/v1/lineage/nodes/{dataNodeId}/relationships
Delete all edges for a node
LineageService_DeleteLineageRelationshipsForNode 1 param → 200default
GET
/api/v1/lineage/nodes/{dataNodeId}/relationships
Get all edges for a node
LineageService_GetLineageRelationshipsForNode 1 param → 200default
POST
/api/v1/lineage/integrations/{integrationId}/lineage/workflow
Queue a lineage collection workflow for an integration
LineageService_QueueLineageForIntegration 1 param → 200default
POST
/api/v1/lineage/sources/{sourceId}/lineage/workflow
Queue a lineage collection workflow for a source
LineageService_QueueLineageForSource 1 param → 200default

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are generatedDataNode (14 properties), generatedCreateDataNodeRequest (7 properties), generatedLineageRelationship (6 properties), runtimeError (4 properties). Each schema is shown below with its type and property counts.

generatedEmpty
object
generatedLineageRelationship
object
6 properties
generatedGetLineageRelationshipsForNodeResponse
object
2 properties
generatedCreateDataNodeRequest
object
7 properties
generatedIntegrationPartner
string
generatedWarehouseType
string
protobufAny
object
2 properties
generatedGetDownstreamDataNodesRequest
object
3 properties
generatedDeleteLineageRelationshipsForNodeResponse
object
1 property
generatedWorkflowProcessingType
string
runtimeError
object
4 properties
generatedDataNode
object
14 properties
generatedCreateLineageRelationshipRequest
object
2 properties
generatedGetDownstreamDataNodesResponse
object
1 property
generatedDataNodeType
string
- DATANODETYPEMCSTRATEGYFOLDER: STRATEGY Formerly known as MicroStrategy - DATANODETYPEAIAGENTSNOWFLAKEINTELLIGENCE: AIAGENT prefix: AI agents surfaced on the…
generatedWorkflowResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bigeye-lineageservice-api-openapi.yml Raw ↑

Other APIs Bigeye publishes across the network.

Bigeye MCP Gateway
Bigeye Agent Service API
Bigeye API Key Service API
Bigeye Catalog Rebuilds Service API
Bigeye Classifier Service API
Bigeye Collection Service API
Bigeye Collection V2 Service API
Bigeye Column Service API
Bigeye Company Service API
Bigeye Comparison Table Service API
Bigeye Config Service API
Bigeye Custom Rule Service API
Where this information came from

This is an independent, third-party profile of Bigeye Lineage Service API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.