Apollo

Fresh depth-11 runtime review passed for Apollo data.enrich_person through Rhumb Resolve. Managed and direct executions matched on name, title, organization name, LinkedIn URL, and email status for the same live email input.

Fresh current-depth runtime rerun passed for Apollo data.enrich_person through Rhumb Resolve again. Managed and direct executions matched on name, title, organization_name, linkedin_url, and email_status for the same live email input.

Fresh current-depth runtime rerun passed for Apollo data.enrich_person through Rhumb Resolve again. Managed and direct executions matched on name, title, organization_name, linkedin_url, and email_status for the same live email input.

Fresh current-depth runtime rerun passed for Apollo data.enrich_person through Rhumb Resolve. Managed and direct executions matched on name, title, organization_name, linkedin_url, and email_status for the same live email input.

Live Rhumb-managed `data.enrich_person` execution for `tim@apple.com` matched direct Apollo control on name, title, organization, LinkedIn URL, and email status using the fixed shorthand execute path.

Fresh runtime review on Apollo people matching showed Rhumb Resolve and direct Apollo control agreeing on the returned person, title, organization, and LinkedIn profile for the same email lookup.

Rhumb-managed data.enrich_person executed successfully against Apollo (200 upstream). Direct Apollo API returned matching person record. Telemetry confirmed healthy. Credential injection and billing worked correctly.

REST API at api.apollo.io/v1/ with JSON payloads. People enrichment: POST to /people/match with email, name, or LinkedIn URL — returns contact details, company info, and phone numbers when available. Company enrichment: POST to /organizations/enrich with domain — returns firmographic data. People Search: POST to /mixed_people/search with query filters (person_titles, person_locations, organization_num_employees_ranges, etc.) — returns paginated results. Email sequence management: create, start, stop, and monitor sequences. The API design is functional but some endpoints use POST for what are conceptually GET operations (search). Response payloads include credit usage information. Pagination uses page/per_page parameters. Webhook support for engagement events.

API key authentication via api_key query parameter or X-Api-Key header. Keys are generated per-user in account settings. The API key grants access to the user's account with their role permissions. No OAuth for third-party integrations — the API is designed for direct integration. Credit-based pricing means each enrichment or search operation consumes credits from the account's allocation. Agents must track credit consumption to avoid exhaustion. Free accounts get limited credits. No fine-grained API key scoping — a key either has full access or doesn't exist. No temporary credentials. For agents, the main security consideration is that enriched data may contain personally identifiable information subject to privacy regulations.

Apollo.io combines a B2B contact/company database with sales engagement tools (email sequences, dialer, LinkedIn integration). For agents, the primary value is the enrichment and search API: look up people by email, name, or domain and retrieve contact details, company information, job titles, and social profiles. The People Search API enables programmatic prospecting — agents can query for contacts matching specific criteria (title, location, company size, industry). Company enrichment provides firmographic data. The engagement API manages email sequences and tracks opens/clicks. Main considerations: data accuracy varies (no B2B database is 100% accurate), credit-based pricing means agents must budget API usage, and the free tier has meaningful limitations. The API covers the sales intelligence use case well for agents building lead generation or CRM enrichment workflows.

API errors return HTTP status codes with JSON error messages. 401 for invalid key, 422 for validation errors, 429 for rate limits. Rate limits vary by plan: free accounts are tightly limited, paid accounts get more generous allowances. The most relevant 'error' for agents isn't HTTP-level — it's data quality: enrichment results may return incomplete or outdated information. Contact details change frequently; email addresses may be invalid. Agents relying on Apollo data should validate enriched emails before use and handle partial results gracefully. Credit depletion returns a specific error. Search results may include fewer results than expected when the database lacks matches. Webhook delivery for engagement events is generally reliable.

API documentation at apolloio.github.io/apollo-api-docs provides endpoint reference with parameters and response examples. The documentation covers enrichment, search, engagement, and account management endpoints. Examples use curl commands. The documentation is adequate for core use cases but thinner on edge cases, error handling specifics, and best practices for credit optimization. No official SDKs — agents use raw HTTP. Third-party wrapper libraries exist for Python and Node with varying quality. The in-app API documentation (Settings → Integrations → API) provides key management and basic usage information. Community resources are limited compared to more developer-focused platforms. For agents, the enrichment endpoint docs are the most important starting point.