Zalify · Developers

Build with Zalify, from the terminal to the storefront.

Verified entry points for developers and AI agents using the Zalify CLI, installing first-party tracking, or finding machine-readable product guidance.

Agent-ready path

01

zalify brand init

02

zalify brand validate

03

zalify shop create

04

zalify ads report

Official resources

Start from a published contract.

Each resource below is public, crawlable, and named for Zalify so people, search engines, and agents can find the same source of truth.

01

CLI

Zalify CLI command reference

The complete command model, authentication flow, golden path, and local file contracts for brand, shop, ads, and theme operations.

Open cli.txt

02

Integration

Zalify Pixel implementation guides

Install first-party tracking, connect Shopify, manage consent, and forward conversion events to supported advertising platforms.

Open Pixel docs

03

Discovery

Zalify agent and crawler resources

Use llms.txt for when-to-use guidance, Markdown representations for clean content, and the XML sitemap for complete URL discovery.

Open llms.txt

04

Releases

Zalify CLI changelog

Every published CLI version, newest first, with highlights and the smaller changes. The same entries zalify changelog prints.

Open changelog
Events API

Send your own events to start email flows.

Record what happens in your site, app or backend — a quiz result, a confirmed booking — and let merchants start, filter and end flows on it in Zalify. Event names need no registration.

  • Find the person by customer.externalId, then email, then phone. A new email becomes a contact, with no email subscription or consent.
  • Give each event a uniqueId (or send an Idempotency-Key header). The same event again returns the first one with duplicate: true and starts nothing, so retries are safe.
  • Up to 100 events per batch request. Keys share a limit of 120 requests a minute, and a batch counts as one.
  • Events more than a day old are recorded but don't start or end flows. Recording events is free; flows bill only for the emails they send.
  • Needs an API key with the Track events permission, created in Settings → Developer.

curl

curl -X POST https://app.zalify.com/api/v1/events \
  -H "Authorization: Bearer $ZALIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "event": "Quiz Completed",
    "customer": { "email": "ada@example.com" },
    "properties": { "result": "dry skin", "score": 82 },
    "uniqueId": "quiz-session-8f2c"
  }'

@zalify/sdk 0.5

import { Zalify } from "@zalify/sdk";

const zalify = new Zalify(process.env.ZALIFY_API_KEY);

await zalify.events.track({
  event: "Quiz Completed",
  customer: { email: "ada@example.com" },
  properties: { result: "dry skin", score: 82 },
  uniqueId: "quiz-session-8f2c",
});

Availability

Documented means supported.

Zalify's public API is documented in an OpenAPI specification at https://app.zalify.com/api/v1/openapi, with a readable reference at https://app.zalify.com/api/v1/reference. Zalify's MCP server is published at https://app.zalify.com/api/mcp: Claude and other MCP apps connect with Zalify sign-in, read workspace data and prepare drafts. Before building against an undocumented API, webhook, or partner integration, contact Zalify to confirm the supported surface.

Contact Zalify