instantly-upgrade-migration

name	instantly-upgrade-migration
description	Migrate Instantly.ai integrations from API v1 to v2. Use when upgrading from deprecated v1 endpoints, updating authentication, or migrating endpoint paths and request formats. Trigger with phrases like "instantly v1 to v2", "instantly api migration", "instantly upgrade", "instantly deprecated", "migrate instantly api".
allowed-tools	Read, Write, Edit, Bash(npm:*), Grep
version	1.12.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","instantly","migration","upgrade"]
compatibility	Designed for Claude Code

Instantly Upgrade Migration: API v1 to v2

Overview

Migrate from Instantly API v1 (deprecated January 2026) to API v2. Key changes: Bearer token auth replaces query-string API keys, REST-standard endpoints replace legacy paths, scoped API keys replace single global key, and cursor-based pagination replaces offset pagination. Existing v1 integrations via Zapier/Make continue working, but new integrations must use v2.

Prerequisites

• Existing Instantly API v1 integration
• Access to Instantly dashboard to generate v2 API keys
• Understanding of Bearer token authentication

Migration Map

Authentication Change

// v1: API key as query parameter
// DEPRECATED — do not use
const v1Url = `https://api.instantly.ai/api/v1/campaign/list?api_key=${API_KEY}`;

// v2: Bearer token in Authorization header
const v2Response = await fetch("https://api.instantly.ai/api/v2/campaigns", {
  headers: { Authorization: `Bearer ${API_KEY}` },
});

Endpoint Migration Table

Operation	v1 Endpoint	v2 Endpoint	Method Change
List campaigns	GET /api/v1/campaign/list	GET /api/v2/campaigns	Same
Get campaign	GET /api/v1/campaign/get	GET /api/v2/campaigns/{id}	Query -> Path param
Create campaign	POST /api/v1/campaign/create	POST /api/v2/campaigns	REST standard
Launch campaign	POST /api/v1/campaign/launch	POST /api/v2/campaigns/{id}/activate	New path
Pause campaign