Switch execution, keep the assistant contract familiar.

Positioning boundary

Aywa Runtime is independently developed. Third-party product names are used only to identify supported import sources, compatibility fields, or customer migration context.

Migration flow

Importer endpoints

The runtime exposes import routes for compatibility workflows. Source ids can be mapped to runtime ids for later lookup and phased cutovers.

{
  "sourceFormat": "compatible_assistant_export",
  "compatibilityProfile": "generic_assistant_v1",
  "sourcePlatform": "vapi",
  "apiKey": "source_private_key",
  "dryRun": true,
  "mode": "upsert",
  "resourceTypes": ["assistants", "tools", "phoneNumbers", "credentials"]
}

What changes in your application code

The importer migrates compatible runtime resources; it does not rewrite or deploy your application. Your backend must point to the private runtime, use runtime IDs, and verify Aywa webhook signatures. The generated Application migration kit in the runtime dashboard contains an environment template, ID map, SQL, call example, webhook verifier, and cutover checklist for the completed import.

Before and after: outbound phone call

The business payload remains familiar. The material changes are the client, private runtime endpoint, organization scope, mapped IDs, and explicit idempotency.

import { VapiClient } from "@vapi-ai/server-sdk";

const vapi = new VapiClient({
  token: process.env.VAPI_API_KEY,
});

await vapi.calls.create({
  assistantId: process.env.VAPI_ASSISTANT_ID,
  phoneNumberId: process.env.VAPI_PHONE_NUMBER_ID,
  customer: { number: "+33611111111" },
});

import { AywaRuntimeClient } from "@aywa-ai/runtime-sdk";

const runtime = new AywaRuntimeClient({
  baseUrl: process.env.AYWA_RUNTIME_BASE_URL,
  apiKey: process.env.AYWA_RUNTIME_API_KEY,
  organizationId: process.env.AYWA_RUNTIME_ORGANIZATION_ID,
});

await runtime.calls.createPhone({
  assistantId: process.env.AYWA_RUNTIME_ASSISTANT_ID,
  phoneNumberId: process.env.AYWA_RUNTIME_PHONE_NUMBER_ID,
  customer: { number: "+33611111111" },
}, {
  idempotencyKey: "outbound-call-customer-123-attempt-1",
});

Reuse the same idempotency key when retrying the same business operation. Generate a new key only for a genuinely new call request.

Webhook cutover

Aywa Runtime sends the stable { "message": ... } body used by compatible server-event integrations. The trust boundary changes: verify the raw request body with the runtime-owned signing secret before parsing or executing a tool.

import { verifyAywaWebhookSignature } from "@aywa-ai/runtime-sdk";

const verified = await verifyAywaWebhookSignature({
  secret: process.env.AYWA_RUNTIME_WEBHOOK_SECRET,
  rawBody,
  signature: request.headers["x-aywa-signature"],
  toleranceSeconds: 300,
});

if (!verified) throw new Error("Invalid Aywa Runtime webhook signature");

const { message } = JSON.parse(rawBody);

Browser and mobile integrations

A source browser SDK is not replaced by the server SDK. Create the web call from a trusted backend, obtain the runtime WebRTC session, then give only the short-lived session material to the browser. Private runtime API keys remain server-side.

ID mapping and customer SQL patches

The migration assistant is available inside the private runtime dashboard under Migration. It imports compatible resources, builds a source-id to runtime-id mapping table, and can generate a reviewable SQL pack for the customer-owned tables that still store source ids.

{
  "organizationId": "org_...",
  "sourcePlatform": "vapi",
  "mode": "upsert",
  "sqlMappingTable": "public.aywa_import_id_mappings",
  "sqlReferenceUpdates": [
    {
      "tableName": "public.calls",
      "columnName": "assistant_id",
      "resourceType": "assistants",
      "filterColumn": "workspace_id",
      "filterValue": "customer_workspace_123",
      "valueCast": "text"
    },
    {
      "tableName": "public.tool_runs",
      "columnName": "tool_id",
      "resourceType": "tools",
      "valueCast": "uuid"
    }
  ]
}

The copied fullMigration SQL contains the mapping-table schema, mapping upserts, reference previews, reference updates, and BEGIN/COMMIT boundaries. Third-party names in this workflow identify the migration source only; the resulting resources run on Aywa Runtime.

Validation checklist

Compatibility boundary

Aywa Runtime can import compatible assistant configurations from existing customer-owned exports. The import profile identifies the format being mapped; it does not imply affiliation, endorsement, or shared ownership with any third-party platform.