AP

apollo-upgrade-migration

Migrate Apollo.io API versions and manage breaking changes safely.

Install

mkdir -p .claude/skills/apollo-upgrade-migration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7406" && unzip -o skill.zip -d .claude/skills/apollo-upgrade-migration && rm skill.zip

Installs to .claude/skills/apollo-upgrade-migration

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.

Manage Apollo.io API upgrades and endpoint migrations.
54 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Audit existing API endpoint usage
  • Identify deprecated API patterns
  • Generate migration rules for breaking changes
  • Implement feature-flagged migration paths
  • Perform shadow testing of API responses

How it works

The skill audits the codebase for deprecated patterns using grep, then provides a mapping to new endpoints and authentication methods. It supports safe transitions through feature flags and shadow testing to compare results between old and new implementations.

Inputs & outputs

You give it
Existing codebase and target API version
You get back
Audit report and migration code patches

When to use apollo-upgrade-migration

  • Audit existing Apollo API endpoint usage
  • Manage transition from deprecated endpoints
  • Implement compatibility layers for API upgrades
  • Validate API migration safety

About this skill

Apollo Upgrade Migration

Current State

!npm list axios 2>/dev/null | head -5

Overview

Plan and execute safe upgrades for Apollo.io API integrations. Apollo has made several breaking changes historically (query param auth to header auth, endpoint URL changes, new search endpoints). This covers auditing current usage, building compatibility layers, and migrating safely.

Prerequisites

  • Valid Apollo API key
  • Node.js 18+

Instructions

Step 1: Audit Current API Usage

// src/scripts/api-audit.ts
import { execSync } from 'child_process';

interface EndpointUsage { endpoint: string; files: string[]; status: 'current' | 'deprecated'; }

const ENDPOINT_MAP = [
  // Current endpoints
  { pattern: '/mixed_people/api_search', status: 'current' as const },
  { pattern: '/mixed_companies/search', status: 'current' as const },
  { pattern: '/people/match', status: 'current' as const },
  { pattern: '/people/bulk_match', status: 'current' as const },
  { pattern: '/organizations/enrich', status: 'current' as const },
  { pattern: '/contacts/search', status: 'current' as const },
  { pattern: '/emailer_campaigns', status: 'current' as const },
  { pattern: '/email_accounts', status: 'current' as const },
  { pattern: '/opportunities', status: 'current' as const },
  // Deprecated patterns
  { pattern: '/people/search', status: 'deprecated' as const },  // old search endpoint
  { pattern: '/organizations/search', status: 'deprecated' as const },
  { pattern: 'api_key.*=', status: 'deprecated' as const },  // query param auth
  { pattern: 'api.apollo.io/v1', status: 'deprecated' as const },  // old base URL (should be /api/v1)
];

function auditUsage(srcDir: string = 'src'): EndpointUsage[] {
  const results: EndpointUsage[] = [];
  for (const ep of ENDPOINT_MAP) {
    try {
      const files = execSync(
        `grep -rl "${ep.pattern}" ${srcDir} --include="*.ts" --include="*.js" 2>/dev/null`,
        { encoding: 'utf-8' },
      ).trim().split('\n').filter(Boolean);
      if (files.length > 0) results.push({ endpoint: ep.pattern, files, status: ep.status });
    } catch { /* no matches */ }
  }

  console.log('=== Apollo API Usage Audit ===');
  for (const r of results) {
    const icon = r.status === 'deprecated' ? 'WARN' : 'OK';
    console.log(`${icon} ${r.endpoint} (${r.files.length} files)`);
    r.files.forEach((f) => console.log(`     ${f}`));
  }
  const deprecated = results.filter((r) => r.status === 'deprecated');
  if (deprecated.length > 0) {
    console.log(`\n${deprecated.length} deprecated pattern(s) found — migration needed`);
  }
  return results;
}

Step 2: Migration Map — Old to New

// src/migration/apollo-migration-map.ts
interface MigrationRule {
  description: string;
  find: string | RegExp;
  replace: string;
  breaking: boolean;
}

const MIGRATION_RULES: MigrationRule[] = [
  // Auth: query param -> header
  {
    description: 'Move API key from query param to x-api-key header',
    find: /params:\s*\{[^}]*api_key[^}]*\}/g,
    replace: "headers: { 'x-api-key': process.env.APOLLO_API_KEY! }",
    breaking: true,
  },
  // Base URL
  {
    description: 'Update base URL from /v1 to /api/v1',
    find: 'api.apollo.io/v1',
    replace: 'api.apollo.io/api/v1',
    breaking: true,
  },
  // People Search endpoint
  {
    description: 'Migrate people search to new endpoint',
    find: '/people/search',
    replace: '/mixed_people/api_search',
    breaking: true,
  },
  // People Search parameters
  {
    description: 'Rename q_organization_domains to q_organization_domains_list',
    find: 'q_organization_domains:',
    replace: 'q_organization_domains_list:',
    breaking: false,
  },
  // Organization Search endpoint
  {
    description: 'Migrate org search to new endpoint',
    find: '/organizations/search',
    replace: '/mixed_companies/search',
    breaking: true,
  },
];

Step 3: Build a Feature-Flagged Migration

// src/migration/feature-flags.ts
const flags = {
  useNewSearchEndpoint: process.env.FF_NEW_SEARCH === 'true',
  useHeaderAuth: process.env.FF_HEADER_AUTH === 'true',
  useNewBaseUrl: process.env.FF_NEW_BASE_URL === 'true',
};

export function getSearchEndpoint(): string {
  return flags.useNewSearchEndpoint ? '/mixed_people/api_search' : '/people/search';
}

export function getBaseUrl(): string {
  return flags.useNewBaseUrl ? 'https://api.apollo.io/api/v1' : 'https://api.apollo.io/v1';
}

export function getAuthConfig(): Record<string, any> {
  if (flags.useHeaderAuth) {
    return { headers: { 'x-api-key': process.env.APOLLO_API_KEY! } };
  }
  return { params: { api_key: process.env.APOLLO_API_KEY! } };
}

Step 4: Run Parallel Comparison

async function shadowTest(searchParams: Record<string, any>) {
  const oldClient = axios.create({ baseURL: 'https://api.apollo.io/v1', params: { api_key: process.env.APOLLO_API_KEY } });
  const newClient = axios.create({ baseURL: 'https://api.apollo.io/api/v1', headers: { 'x-api-key': process.env.APOLLO_API_KEY! } });

  const [oldResult, newResult] = await Promise.allSettled([
    oldClient.post('/people/search', searchParams),
    newClient.post('/mixed_people/api_search', searchParams),
  ]);

  console.log('Shadow test results:');
  console.log(`  Old: ${oldResult.status === 'fulfilled' ? oldResult.value.status : 'FAIL'}`);
  console.log(`  New: ${newResult.status === 'fulfilled' ? newResult.value.status : 'FAIL'}`);

  if (oldResult.status === 'fulfilled' && newResult.status === 'fulfilled') {
    const oldCount = oldResult.value.data.people?.length ?? 0;
    const newCount = newResult.value.data.people?.length ?? 0;
    console.log(`  Results match: ${oldCount === newCount} (old: ${oldCount}, new: ${newCount})`);
  }
}

Step 5: Post-Migration Cleanup

# Find remaining deprecated patterns
grep -rn "api.apollo.io/v1[^/]" src/ --include="*.ts" || echo "No old base URL found"
grep -rn "api_key.*=" src/ --include="*.ts" | grep -v "x-api-key" || echo "No query param auth found"
grep -rn "/people/search" src/ --include="*.ts" | grep -v "mixed_people" || echo "No old search endpoint found"

echo "Cleanup complete. Remove feature flags: FF_NEW_SEARCH, FF_HEADER_AUTH, FF_NEW_BASE_URL"

Output

  • API usage audit identifying current and deprecated patterns
  • Migration rule map for auth, base URL, and endpoint changes
  • Feature-flagged migration with environment variable controls
  • Shadow testing for comparing old vs new API responses
  • Post-migration cleanup script

Error Handling

IssueResolution
Audit finds deprecated patternsApply migration rules file by file
Shadow test results differCheck parameter name changes (e.g., q_organization_domains vs _list)
Feature flag issuesDisable flag immediately (FF_*=false)
Old endpoints still workApollo maintains backward compatibility, but migrate proactively

Resources

Next Steps

Proceed to apollo-ci-integration for CI/CD setup.

When not to use it

  • When no breaking changes are expected

Prerequisites

Valid Apollo API keyNode.js 18+

Limitations

  • Requires manual review of shadow test results
  • Migration rules must be applied file by file

How it compares

It automates the identification of deprecated patterns and provides a verification mechanism via shadow testing, unlike manual refactoring.

Compared to similar skills

apollo-upgrade-migration side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
apollo-upgrade-migration (this skill)125dCautionIntermediate
mcp-builder1363moReviewAdvanced
telegram-bot-builder1066moReviewIntermediate
telegram-mini-app626moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

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).

136215

telegram-bot-builder

davila7

Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.

106130

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.

62163

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.

48165

oracle

openclaw

Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).

17126

n8n-expression-syntax

czlonkowski

Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.

6111

Search skills

Search the agent skills registry