API — GraphIQ.ai

The B2B Identity Graph via REST: Semantic JSON-LD, Predictable Throttling.

GraphIQ.ai's REST API provides developer and data engineering teams with programmatic access to our full B2B identity graph. Query 287M organizations, 393M professionals, and billions of operational signals across unified v2 endpoints. Every request returns clean, semantic JSON-LD payloads.

Power your data workflows with Abstract Syntax Tree (AST) queries.

Traditional B2B data REST APIs force engineers to use flat query parameters. GraphIQ.ai introduces an Abstract Syntax Tree (AST) search layer. By combining nested logical operators (and, or, not, should) with precise field specifiers, you can execute highly advanced queries within a single transactional payload.

Example AST Query

{
  "query": {
    "and": [
      { "field": "industry", "eq": "SaaS" },
      "should": [
        { "field": "signal", "eq": "funding" },
        { "not": { "field": "hq", "eq": "US" } }
      ]
    ]
  }
}

Core v2 endpoint architecture.

All v2 endpoints accept structured POST bodies with AST query trees. Responses return typed JSON-LD payloads with canonical entity URIs, provenance metadata, and relationship references.

v2 REST API endpoint directory.

POST/api/v2/organizations/search: Core engine for company discovery across entity names, corporate trees, revenue, technology stacks, geography.
POST/api/v2/people/search: Track 393M professionals by title, department, seniority, skills, verified contact details.
POST/api/v2/news/search: Stream real-time operational trigger events filtered by org ID, keyword, date, sentiment.
CapabilitySignal feed: Pull signals for watched entities by signal type, date range, or recency.
CapabilityLookalike discovery: Submit seed set of entity IDs, return ranked matches with rationale.
CapabilityBuying group resolution: Query decision-making units within an account.

How does authentication work?

API key: Per workspace, from workspace settings.
Base URL: https://api.graphiq.ai/v2/
Response format: JSON-LD with entity URIs.

Frequently asked questions

What is the difference between the REST API and the MCP server?
REST for traditional integrations — ETL pipelines, batch enrichment. MCP for AI agents that need to query the graph as part of an active reasoning loop.