Store Events API Reference (Custom Stores)

The ReploChat store events API lets a custom-built store, a headless checkout or a WooCommerce plugin tell ReploChat that something happened to an order. Each event runs the same WhatsApp automations as a Shopify or WooCommerce webhook: order confirmation, COD confirmation, order shipped, order cancelled and the abandoned cart reminder. This page is the complete developer reference: endpoint, authentication, every accepted field, rate limit, responses and errors.

Shopify and WooCommerce stores don't need this API. Connect them on the Integrations page and ReploChat creates the webhooks for you, as described in Connect Shopify & WooCommerce. Use the API when your store is custom-built, or when a plugin (for example a cart-recovery plugin) has to send events itself.

What the store events API can and can't do

Before you call the API

1. Make sure your plan includes store integrations. If it doesn't, every call returns 403. See pricing.
2. In ReploChat open Integrations → Connect a store, choose Custom store (API), give it a Name and set Country for numbers without a code (Pakistan by default). A custom store has no webhooks; it only receives events through this API.
3. On the store's tab, set up each automation you want: pick the WhatsApp number and an approved template, map the template variables to order fields, turn it on and Save. An event with no active automation is logged as skipped.
4. In the API keys box, type a Name (for example "Website plugin"), choose the store under Runs the automations of and click Create key.
5. Copy the key straight away. It is shown once ("Copy this key now — it won't be shown again"). ReploChat keeps only a SHA-256 hash; the list shows just the first characters.

Endpoint and authentication

POST https://replochat.com/api/v1/store-events
Authorization: Bearer rpc_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Content-Type: application/json

• Keys start with rpc_. Send the key as a Bearer token in the Authorization header.
• Responses are always JSON, including validation errors, whatever Accept header you send.
• Each key belongs to one store connection, so the event runs that store's automations.
• Rate limit: 120 requests per minute, counted per client IP. Above that you get 429 Too Many Requests with a Retry-After header.

Request body

The body has an event, an optional event_id and an order object.

Fields not in this table are ignored.

What each event does

order_placed

Sends the Order confirmation automation. If the order is COD and the COD confirmation automation is on, the customer gets that template instead, with Confirm and Cancel buttons. When they tap one, ReploChat replies with your "Reply after Confirm" or "Reply after Cancel" text and records the answer under Recent events. Because a custom store has no API for ReploChat to call, your system is not updated; check the log or ask your team to act on it. If checkout_id matches a waiting abandoned cart, that reminder is cancelled.

order_shipped and order_cancelled

Send the Order shipped and Order cancelled automations. Include tracking_number and tracking_url on shipped events if your template uses them. If a mapped variable comes out empty and you set no fallback text, the event fails with "Missing template values".

abandoned_cart

Abandoned-cart reminders are automatic only for Shopify. WooCommerce has no abandoned-cart webhook, so a WooCommerce store (or a custom store) needs a cart-recovery plugin or script that posts abandoned_cart events to this API.

The reminder doesn't send straight away. ReploChat waits for the delay set on the Abandoned cart reminder automation, then sends it. If you don't send checkout_id, order.id is used. While the reminder waits:

• Sending the same abandoned cart again (same event_id, or no event_id and the same order.id) updates its details. Add "completed": true to cancel it.
• An order_placed with the same checkout_id cancels it with "Customer completed the order".

Example: a COD order from Pakistan

curl -X POST https://replochat.com/api/v1/store-events \
  -H "Authorization: Bearer rpc_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "event": "order_placed",
    "event_id": "order-1001-placed",
    "order": {
      "id": "1001",
      "number": "#1001",
      "customer_name": "Ayesha Khan",
      "phone": "03001234567",
      "country": "PK",
      "total": 4999,
      "currency": "PKR",
      "items": [{ "name": "Lawn suit 3-piece", "quantity": 1 }],
      "payment_method": "cod",
      "checkout_id": "cart-88f2"
    }
  }'

Example: an abandoned cart

{
  "event": "abandoned_cart",
  "event_id": "cart-88f2",
  "order": {
    "id": "cart-88f2",
    "customer_name": "Ayesha Khan",
    "phone": "+923001234567",
    "total": 4999,
    "currency": "PKR",
    "checkout_url": "https://shop.example.com/cart/88f2"
  }
}

Responses

Retries and duplicates

• With event_id, the same id sent again to the same store is a duplicate, whatever the event type. Make it unique per event, e.g. order-1001-shipped.
• Without event_id, the same event for the same order.id is a duplicate. That means you can't send two order_shipped events for one order without event ids.
• On a timeout or a 5xx, retry with the same body. Back off on 429.

Good to know

• Customers who replied STOP are never messaged.
• Each chat gets the store's label, and the message appears in the shared inbox like any other.
• Meta bills template messages to your own WhatsApp Business Account by category and country. ReploChat adds no markup.

Related guides

• Connect Shopify & WooCommerce to WhatsApp
• Create WhatsApp template messages that get approved
• Use the shared team inbox
• All ReploChat integrations