Weave by Loom Loyalty

Build with Weave by Loom Loyalty.

Weave is the rules engine and API behind every Loom Loyalty program. Send events, read balances and tiers, and get signed webhooks back, over plain REST.

Book a callRead the docs
First call

A customer in one request.

Create an API key under Developers → API Keys, then send it as a bearer token. Every response comes back in the same envelope, with the created resource under data.

Follow the Quick Start to read the customer back, or do the same with fetch from any language.

Request
curl -X POST https://api.loomloyalty.com/customers \
  -H "Authorization: Bearer $LOOM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "identity": { "firstName": "Ada", "lastName": "Lovelace" },
    "externalId": "user-1001"
  }'
Response
{
  "success": true,
  "eventId": "…",
  "eventDateTime": "…",
  "data": {
    "customerId": "…",
    "externalId": "user-1001"
  }
}
Events in, loyalty out

One pipeline from signal to reward.

  1. Send an event

    Your app, store or data pipeline tells Weave a customer did something: a purchase, a check-in, a referral.

  2. Rules run

    Event rules turn it into outcomes: award points, move a tier, progress a target, grant a badge.

  3. The ledger records it

    Every balance change lands in an append-only ledger, so a balance is always explained by its history.

  4. Your stack hears back

    Signed webhooks push the result to your systems, and the API reads the new state on demand.

Webhooks

Stop polling.

Register an HTTPS endpoint, choose the event types it receives, and Weave sends a signed POST for each one. Verify the signature with the endpoint's secret, and deduplicate on eventId so a redelivery is processed once.

  • Retries for deliveries that fail or time out
  • Test messages, per-attempt history and replays after an outage
  • Connectors for Zapier, Make, Segment, Inngest and Slack
Delivery
{
  "messageId": "…",
  "eventType": "…",
  "eventId": "…",
  "payload": {}
}
Tools

Everything you build with.

  • REST API

    Customers, programs, currencies, tiers, offers, coupons, targets, badges and events, as plain JSON resources.

    API reference →

  • Webhooks

    Signed deliveries with retries, test messages and replays, plus connectors for Zapier, Make, Segment, Inngest and Slack.

    Webhooks guide →

  • AI assistants over MCP

    A remote MCP server lets Claude, ChatGPT, Cursor and other clients manage a program, limited to what your role allows.

    Connect an assistant →

  • Core concepts

    How customers, programs, ledgers and the event engine fit together before you write a line of code.

    Read the concepts →
Environments

Build in development, ship to production.

  • Separate environments

    Each organization has its own environments, each with its own data, API keys and limits.

  • Keys scoped by role

    Give each integration only the access it needs, and revoke a key without touching the others.

  • Predictable limits

    Per-environment rate limits, one error format and the same paging on every list endpoint.

Next step

See Weave on your data.

Book a call and we'll walk through your events, your rules and your stack. Want the architecture first? Read how the platform is built.

Book a callHow the platform is built