API Keys

API Keys give you programmatic access to MarketGeist's intelligence platform. Use them to integrate market reports, competitor data, and intelligence into your own applications, internal dashboards, or automated workflows.

Explain Like I'm 5

An API key is like a special password that lets one computer talk to another. When you want your own website or app to ask MarketGeist for market data, it needs to show this special password to prove it's allowed. Without the key, MarketGeist won't answer. It's like having a VIP pass to a concert — show the pass, and you get in.

What Does It Do?

API Keys enable programmatic access to MarketGeist's REST API. With an API key, you can create reports, list competitors, fetch market data, and access all intelligence features without using the web dashboard. Each key has configurable scopes that control which API endpoints it can access.

Why It Matters

Custom integrations — embed MarketGeist intelligence into your own internal tools and dashboards

Automation — schedule report generation, data pulls, and competitive updates via scripts or cron jobs

Workflow integration — connect to Zapier, n8n, or custom automation pipelines

White-label — agencies can use the API to power client-facing intelligence deliverables

Data pipeline — feed MarketGeist data into your data warehouse, BI tools, or CRM

How to Create an API Key

Go to Dashboard → API Keys

The API Keys page shows your existing keys and an option to create new ones.

Click "Create API Key"

Give the key a descriptive name (e.g., "Production Integration" or "Zapier Automation") and select the scopes (which endpoints it can access).

Copy and secure the key

The full key is shown only once at creation. Copy it immediately and store it securely (e.g., environment variable, secrets manager). The key starts with "mg_live_".

Use the key in API requests

Include the key in the X-API-Key header of your HTTP requests to the MarketGeist API.

API Request — Example

cURL — List your reports

curl -X GET "https://marketgeist.com/api/v1/public/reports" \
  -H "X-API-Key: mg_live_your_key_here"

Response

{
  "success": true,
  "data": [
    {
      "id": 42,
      "report_type": "decision_brief",
      "title": "AI Chatbot Market — Global Decision Brief",
      "confidence": 0.87,
      "created_at": "2026-04-14T10:30:00Z"
    }
  ]
}

Available API Scopes

API Key Scopes

Scope	Endpoints Accessible	Description
reports	GET/POST /reports	Create and list market intelligence reports
competitors	GET/POST /competitors	Manage competitor profiles and fetch analysis
seo	GET /seo/*	Access SEO audit results and keyword data
signals	GET /signals	Read market signals
social_trends	GET /social-trends	Access social trend data
market_data	GET /market-data/*	Browse company and industry data

Pro Tip

Create separate API keys for each integration (one for your CRM sync, one for your Zapier workflows, one for your internal dashboard). This way, if one key is compromised or an integration is retired, you can revoke that specific key without affecting the others. Name keys descriptively so you know which one is which.