apollo-hello-world
Provides a minimal, working code example for the Apollo.io People and Enrichment APIs.
Install
mkdir -p .claude/skills/apollo-hello-world && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8267" && unzip -o skill.zip -d .claude/skills/apollo-hello-world && rm skill.zipInstalls to .claude/skills/apollo-hello-world
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a minimal working Apollo.io example.Key capabilities
- →Search for people using organization domains and job titles
- →Enrich individual contact profiles with email and phone data
- →Retrieve organization details including industry and revenue
- →Authenticate API requests using x-api-key headers
- →Handle API responses in TypeScript and Python
How it works
The skill provides code templates to interact with the Apollo.io API base URL using standard HTTP methods for searching and enriching contact or company data. It demonstrates the use of specific headers and request bodies required to authenticate and query the Apollo database.
Inputs & outputs
When to use apollo-hello-world
- →Test Apollo API connectivity
- →Implement contact searching in a project
- →Create data enrichment workflows
- →Understand API authentication requirements
About this skill
Apollo Hello World
Overview
Minimal working example demonstrating the three core Apollo.io API operations: people search, person enrichment, and organization enrichment. Uses the correct x-api-key header and api.apollo.io/api/v1/ base URL.
Prerequisites
- Completed
apollo-install-authsetup - Valid API key configured in
APOLLO_API_KEYenvironment variable
Instructions
Step 1: Search for People (No Credits Consumed)
The People API Search endpoint finds contacts in Apollo's 275M+ database. This endpoint is free — it does not consume enrichment credits, but it also does not return emails or phone numbers.
// hello-apollo.ts
import axios from 'axios';
const client = axios.create({
baseURL: 'https://api.apollo.io/api/v1',
headers: {
'Content-Type': 'application/json',
'x-api-key': process.env.APOLLO_API_KEY!,
},
});
// People Search — POST /mixed_people/api_search
async function searchPeople() {
const { data } = await client.post('/mixed_people/api_search', {
q_organization_domains_list: ['apollo.io'],
person_titles: ['engineer'],
person_seniorities: ['senior', 'manager'],
page: 1,
per_page: 10,
});
console.log(`Found ${data.pagination.total_entries} contacts`);
data.people.forEach((person: any) => {
console.log(` ${person.name} — ${person.title} at ${person.organization?.name}`);
});
return data;
}
searchPeople().catch(console.error);
Step 2: Enrich a Single Person (Consumes 1 Credit)
The People Enrichment endpoint returns full contact details including email and phone.
// Enrich by email, LinkedIn URL, or name+domain combo
async function enrichPerson() {
const { data } = await client.post('/people/match', {
email: '[email protected]',
// Alternative identifiers:
// linkedin_url: 'https://www.linkedin.com/in/...',
// first_name: 'Tim', last_name: 'Zheng', organization_domain: 'apollo.io',
reveal_personal_emails: false,
reveal_phone_number: false,
});
if (!data.person) {
console.log('No match found');
return;
}
const p = data.person;
console.log(`Name: ${p.name}`);
console.log(`Title: ${p.title}`);
console.log(`Email: ${p.email}`);
console.log(`Company: ${p.organization?.name}`);
console.log(`LinkedIn: ${p.linkedin_url}`);
}
Step 3: Enrich an Organization (Consumes 1 Credit)
// Organization Enrichment — GET /organizations/enrich
async function enrichOrg() {
const { data } = await client.get('/organizations/enrich', {
params: { domain: 'apollo.io' },
});
const org = data.organization;
if (!org) { console.log('No org found'); return; }
console.log(`Company: ${org.name}`);
console.log(`Industry: ${org.industry}`);
console.log(`Employees: ${org.estimated_num_employees}`);
console.log(`Revenue: ${org.annual_revenue_printed}`);
console.log(`HQ: ${org.city}, ${org.state}, ${org.country}`);
console.log(`Tech Stack: ${org.current_technologies?.slice(0, 5).map((t: any) => t.name).join(', ')}`);
}
Step 4: Python Equivalent
import os, requests
API_KEY = os.environ['APOLLO_API_KEY']
BASE = 'https://api.apollo.io/api/v1'
HEADERS = {'Content-Type': 'application/json', 'x-api-key': API_KEY}
# People search (free)
resp = requests.post(f'{BASE}/mixed_people/api_search', headers=HEADERS, json={
'q_organization_domains_list': ['apollo.io'],
'person_titles': ['engineer'],
'page': 1, 'per_page': 5,
})
for p in resp.json().get('people', []):
print(f" {p['name']} — {p.get('title', 'N/A')}")
# Org enrichment (1 credit)
resp = requests.get(f'{BASE}/organizations/enrich',
headers=HEADERS, params={'domain': 'apollo.io'})
org = resp.json().get('organization', {})
print(f"Company: {org.get('name')} ({org.get('estimated_num_employees')} employees)")
Output
- People search results (name, title, company — no emails)
- Enriched person with email, phone, LinkedIn URL
- Enriched organization with industry, headcount, revenue, tech stack
Error Handling
| Error | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Missing or invalid x-api-key header | Check APOLLO_API_KEY env var |
| 422 Unprocessable | Malformed request body | Verify JSON payload structure |
| 429 Rate Limited | Exceeded requests/minute | Wait and retry with exponential backoff |
Empty people array | No matches for filters | Broaden titles/seniority or use different domain |
Resources
Next Steps
Proceed to apollo-local-dev-loop for development workflow setup.
When not to use it
- →When you have not completed the apollo-install-auth setup
- →When you lack a valid API key in the APOLLO_API_KEY environment variable
Prerequisites
Limitations
- →People search endpoint does not return emails or phone numbers
- →Enrichment operations consume credits
How it compares
This approach provides pre-configured boilerplate code for Apollo.io API endpoints rather than manually constructing HTTP requests and authentication headers from scratch.
Compared to similar skills
apollo-hello-world side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| apollo-hello-world (this skill) | 0 | 26d | Caution | Beginner |
| openevidence-core-workflow-b | 0 | 26d | Review | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
| telegram-mini-app | 62 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
openevidence-core-workflow-b
jeremylongshore
Execute OpenEvidence DeepConsult workflow for comprehensive medical research. Use when implementing deep research synthesis, complex clinical questions, or when physicians need extensive literature review. Trigger with phrases like "openevidence deepconsult", "deep research", "comprehensive evidence", "literature synthesis".
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
telegram-mini-app
davila7
Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app.
stripe-integration
wshobson
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
backend-dev-guidelines
langfuse
Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).
swapper-integration
shapeshift
Integrate new DEX aggregators, swappers, or bridge protocols (like Bebop, Portals, Jupiter, 0x, 1inch, etc.) into ShapeShift Web. Activates when user wants to add, integrate, or implement support for a new swapper. Guides through research, implementation, and testing following established patterns.