REST API & Webhooks

Listify has a REST API and outbound webhooks for connecting registries to the rest of your stack: an ERP, a CRM, a BI tool, or an in-house integration you are moving over from another registry app.

Availability: Pro plan only.

Full reference: listifyregistry.com/api/v1/docs. Every endpoint, field, error and webhook payload is documented there. The same reference is available inside the app under Settings → API & Shopify Flow → Documentation, and the machine-readable OpenAPI spec is at /api/v1/openapi.json for importing into Postman, Insomnia or a client generator.

What you can do

Area	Endpoints
Registries	List, read, create, update and archive registries. List, add, update and remove their items. Read their orders.
Wishlists	List and read wishlists, their items and their orders.
Webhooks	Create, update, delete and test webhook endpoints.

Getting a token

In the Listify app, go to Settings → API & Shopify Flow → API Access Tokens.
Create a token and choose its scopes: read, registries:write and webhooks:write. Give each integration only what it needs.
Copy the token straight away. It is shown once and cannot be recovered.
Send it on every request as Authorization: Bearer lstk_….

Each token belongs to one shop. Scopes cannot be changed after creation: revoke the token and create a new one.

How purchases reach a registry

There is no API call to mark a registry item as purchased. Listify reads purchases from Shopify orders, so any order that carries the right line item properties lands on the registry by itself, whichever channel created it: the online store, a headless storefront, Shopify POS, or an order your own system creates through the Shopify Admin API.

Put _listify_registry_id, set to the registry's ID, on each gifted line.
For items where the guest picks the variant (gift cards, or products tagged listify:all-variants), also add _listify_registry_item_id, set to the item's id from the items endpoint.
The properties must be on the order when it is created. Adding them to an existing order later is not picked up.

If an order was placed without the properties, it can be attached to a registry by hand in the Listify admin. Before rolling out a custom checkout or in-store integration, place one test order and confirm it shows up on the registry.

Webhooks

Subscribe an HTTPS endpoint and Listify sends signed POST requests when registries and wishlists are created, updated, archived or deleted, and when their items or orders change. The order and item events carry the full changed records, not just counts, so you can sync without calling back. Deliveries are retried on failure, and you can send a test delivery from the API or the app.

Prefer no code? Registry and wishlist events are also available as Shopify Flow triggers. See Emails & Shopify Flow.

Need help?

Email support@listifyregistry.com with what you are connecting. If you are migrating an existing integration from another registry app, tell us how it records purchases today and we will help you map it across.