Plug loyalty into the stack you already run.
Events come in through the API, webhooks or files. Results go out through webhooks, connectors, exports and AI assistants. No rip and replace.
Three ways to send what customers do.
Pick the one your systems already speak. Most teams use more than one.
REST API
Send events, create customers and read balances from any backend, in any language.
Read the guide →Inbound webhooks
Point a store, payment or app platform's webhooks at an ingest source, and each delivery becomes an event.
Read the guide →SFTP file feeds
Drop batch files on a schedule. Each row is checked, turned into an event, and reported back in an output file.
Read the guide →
Tell the rest of your stack what changed.
Every balance change, tier move and reward can reach the tools your teams work in, as it happens.
Webhooks
Signed, retried deliveries to your own HTTPS endpoint for every event type you subscribe to.
Read the guide →Zapier
Start a Zap from any Loom Loyalty event without writing a receiver.
Make
Feed loyalty events into Make scenarios.
Segment
Send loyalty events into Segment, and on to the tools it already feeds.
Inngest
Trigger Inngest functions from loyalty events.
Slack
Connect from the dashboard to post events to a channel as readable messages.
File exports
Scheduled exports to your own S3 bucket or SFTP server, for your warehouse or finance team.
Meet members and agents where they are.
AI assistants over MCP
Claude, ChatGPT, Cursor and any MCP client can manage a program, limited to what your role allows.
Read the guide →Apple and Google Wallet passes
Members carry their balance and tier in Apple Wallet or Google Wallet, and the pass refreshes when they change.
Rewards portal
A branded, hosted portal where members see their points, tier and offers.
File feeds, exports and the rewards portal depend on your plan. See pricing for what each Fit includes.
Don't see your tool?
Anything that can send a webhook or drop a file can feed Loom Loyalty. Book a call and we'll map your stack with you.