Migrating from Calry to Repull — A 5-Minute Guide

If you are using Calry for vacation rental API access, you can migrate to Repull in about 5 minutes. Our schema adapters produce responses that match Calry v1 and v2 exactly.

Step 1: Get your Repull API keys

Sign up at /register and get your sandbox keys. This takes 30 seconds.

Step 2: Change your base URL

// Before (Calry v2)
const BASE = 'https://dev.calry.app/api/v2/vrs'

// After (Repull — Calry v2 compatible by default)
const BASE = 'https://api.repull.dev/v1'

Step 3: Update headers

// Before (Calry)
headers: {
  'Authorization': 'Bearer CALRY_KEY',
  'workspaceId': 'CALRY_WORKSPACE',
  'integrationAccountId': 'CALRY_ACCOUNT',
}

// After (Repull)
headers: {
  'Authorization': 'Bearer sk_live_YOUR_KEY',
  'X-Workspace-Id': 'YOUR_WORKSPACE_ID',
  'X-Account-Id': 'YOUR_ACCOUNT_ID',   // Optional
  'X-Schema': 'calry',                  // Ensures Calry v2 format
}

That is it

Response format is identical. propertyId, checkIn, primaryGuest, financials — all the same field names.

If you are on Calry v1, use X-Schema: calry-v1 instead.

What you get that Calry does not have

• - **AI Operations** (coming soon) — guest responses, intent classification, pricing
• - **CLI + MCP Server** — terminal access and native AI agent tools
• - **5 SDKs** — TypeScript, Python, Go, Ruby, PHP
• - **Sandbox mode** — pre-seeded test data, failure scenarios
• - **Native schema format** — `X-Schema: native` for snake_case if you prefer