Skip to main content
Most teams do not need a bigger list of leads. They need a better way to identify the people who are already in-market. That is what Orbit is for. Orbit turns topic-level research behavior into a usable audience. Instead of guessing who might care about a product, you start with the subjects people are actively researching, then narrow that audience into the slice that actually fits your go-to-market motion. In practice, that usually means:
  • finding the topics that map to your category
  • previewing how much real demand exists around those topics
  • narrowing the audience with filters like seniority, industry, company size, or contact coverage
  • saving the audience so it can refresh over time
  • exporting or querying the people behind that demand
The result is not just a list. It is a living audience built around current intent.

​
What Orbit is

Orbit is Leadpipe’s intent audience API. Use it to find people who are actively researching specific B2B or B2C topics, then narrow those audiences with ICP filters such as company, seniority, industry, department, and contact availability. The typical Orbit workflow looks like this:
  1. Browse or search topics
  2. Preview the audience size
  3. Save an audience
  4. Activate it
  5. Retrieve paginated people data
  6. Export a CSV when needed

​
Base URL

https://api.aws53.cloud

​
Authentication

Authenticated requests can use an X-API-Key header. 
X-API-Key: sk_your_api_key
API keys are scoped to an organization. Create and manage them in Settings > API Keys in the dashboard. Bearer-authenticated requests are also supported. Authenticated traffic keeps the higher rate limit and logs activity to the organization when applicable.

​
Quick start

# 1. Browse available topics
curl "https://api.aws53.cloud/v1/intent/topics/inventory?type=b2b&q=marketing"

# 2. Create an audience
curl -X POST "https://api.aws53.cloud/v1/intent/audiences" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Marketing Directors at Tech Companies",
    "config": {
      "topicIds": [117805, 117890],
      "minScore": 70,
      "filters": {
        "seniority": ["director", "vp", "cxo"],
        "companyIndustry": ["software development", "information technology & services"],
        "hasBusinessEmail": true
      }
    }
  }'

# 3. Activate the audience
curl -X PATCH "https://api.aws53.cloud/v1/intent/audiences/AUDIENCE_ID" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "active"}'

# 4. Get people
curl -X POST "https://api.aws53.cloud/v1/intent/topics/audience" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"audienceId": "AUDIENCE_ID", "limit": 50}'

​
Endpoint groups

​
Discovery

MethodPathAuthPurpose
GET/v1/intent/topics/inventoryNoBrowse all topics
GET/v1/intent/topics/inventory/facetsNoGet filter values with counts
GET/v1/intent/topics/searchNoAutocomplete topic search

​
Audience management

MethodPathAuthPurpose
GET/v1/intent/audience/filtersx-api-keyGet ICP filter values
POST/v1/intent/topics/audience/previewx-api-keyPreview count and masked samples
POST/v1/intent/topics/audiencex-api-keyGet full paginated people data
GET/v1/intent/audiencesx-api-keyList saved audiences
GET/v1/intent/audiences/{id}x-api-keyGet one audience
POST/v1/intent/audiencesx-api-keyCreate an audience
PATCH/v1/intent/audiences/{id}x-api-keyUpdate, activate, or pause
DELETE/v1/intent/audiences/{id}x-api-keyDelete an audience
GET/v1/intent/audiences/{id}/statsx-api-keyGet fill rates
POST/v1/intent/audiences/{id}/exportx-api-keyExport CSV
GET/v1/intent/audiences/{id}/runsx-api-keyList daily runs

​
Errors

StatusCodeMeaning
400VALIDATION_ERRORInvalid request
401AUTHENTICATION_ERRORMissing or invalid API key
403DRAFT_AUDIENCEAudience is draft and must be activated first
403NO_INTENT_CREDITSPlan does not include intent slots
403SLOTS_FULLAll audience slots are in use
404NOT_FOUNDAudience or requested run was not found
429—Rate limit exceeded
500PROCESSING_ERRORQuery failed

​
Rate limits

Auth modeLimit
Unauthenticated2 requests per minute on all intent endpoints
Authenticated via API key or Bearer200 requests per minute