Introducing the Orchly REST API

Today we're launching the Orchly REST API.

The most valuable data in Orchly rarely gets used inside Orchly.

Visibility scores end up in executive dashboards. Rankings get pulled into reports. AI traffic gets joined with revenue data. Share of Voice gets tracked alongside the rest of a company's marketing metrics.

But until now, that data lived exclusively inside our application.

The API changes that.

You can now access the same AI visibility, rankings, citations, search performance, shopping visibility, and AI traffic data you see inside Orchly programmatically and bring it into the tools where your team actually works.

Whether you're building internal dashboards, client reporting, Slack alerts, warehouse pipelines, or entirely new products, your Orchly data can now live wherever you need it.

If it's in Orchly, it's available through the API.

How It Works

We tried hard to make the API boring in the best possible way.

No custom authentication schemes. No unusual conventions. No surprises.

1. Authenticate with an API Key

Generate an API key from your workspace settings and send it with your requests.

Use either an Authorization: Bearer header or an X-API-Key header. Both are supported.

2. Every Request Is Scoped to a Workspace

Requests include an X-Workspace-Id header that determines which workspace data is returned.

This keeps agency and multi-brand setups clean, allowing a single integration to work across multiple workspaces without mixing data.

3. OpenAPI First

The complete API is published as an OpenAPI 3.1 specification.

Generate typed clients in your preferred language, import the schema into your tooling, and build against a documented contract instead of manually maintaining request and response models.

4. Same Data, Same Refresh Schedule

The API exposes the same data used throughout Orchly.

Visibility scores, rankings, citations, AI traffic, shopping visibility, and search performance all come from the same underlying data sources and update on the same cadence as the platform.

curl https://app.orchly.ai/api/v1/visibility \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "X-Workspace-Id: YOUR_WORKSPACE_ID"

What Teams Build With It

The API is less about accessing data and more about deciding where that data belongs.

1. Visibility in Executive Dashboards

Most leadership teams aren't logging into SEO and AI visibility platforms every morning.

By pulling AI Visibility, Share of Voice, rankings, and citation trends into existing business dashboards, visibility becomes part of broader company reporting instead of living in a separate tool.

The result is that the people making decisions actually see the data.

2. Combine Visibility with Business Metrics

Some of the most interesting questions happen when visibility data meets the rest of your business data.

Teams are combining Orchly data with CRM, analytics, advertising, pipeline, and revenue data inside their warehouses to understand how visibility impacts real business outcomes.

Instead of asking which prompts you rank for, you can start asking which prompts drive pipeline, revenue, or customer acquisition.

3. Automate Client Reporting

For agencies, reporting is often where visibility data spends most of its life.

The API makes it possible to pull data from multiple workspaces and generate client-facing reports automatically, without exporting screenshots or manually updating spreadsheets.

Reports stay current, and teams spend more time interpreting data instead of assembling it.

4. Create Custom Alerts

Not every team wants to monitor the same things.

Some care about visibility changes for specific prompts. Others care about citation gains, competitor movement, or traffic shifts.

The API makes it possible to build notifications around the metrics that matter to your business and deliver them directly to Slack, email, or internal systems.

5. Power Internal Tools and Workflows

Many teams already have their own reporting tools, AI assistants, portals, and operational workflows.

The API allows Orchly data to become part of those systems instead of requiring people to switch tools whenever they need visibility insights.

API and MCP

The API and MCP solve the same problem in different ways.

The API is for systems.

MCP is for conversations.

Use the API when you're building dashboards, reports, workflows, automations, and applications.

Use MCP when you want to ask Claude, Cursor, or another AI assistant questions about your visibility data in plain English.

Both provide access to the same Orchly data. They simply fit different ways of working.

Get Started

Generate an API key from your workspace settings and make your first request.

The API documentation includes endpoint references, examples, authentication details, and the complete OpenAPI specification.

If you build something useful on top of it, we'd love to see it.

Many of the best ideas for Orchly have come from seeing how customers use the platform in ways we never expected.