Connect your store to Response360

If your store runs on WooCommerce/WordPress, the official plugin is the fastest path — no code. Download it, upload it in WP Admin, paste your API key, and you are connected.

Download the plugin

The plugin is a ready-to-install ZIP. Download it, then install it from your WordPress admin (steps below).

Response360 for WordPress / WooCommerce

Install it

1. 1In WordPress, go to Plugins → Add New.
2. 2Click Upload Plugin and choose the response360-wordpress.zip you downloaded.
3. 3Click Install Now, then Activate.
4. 4Open Settings → Response360 and paste the API key from your Response360 panel (Integrations).
5. 5Save. Use the built-in Test connection button to confirm the key works.

What the plugin does

Once connected, the plugin gives you four things:

• Order-status WhatsApp notifications. When an order changes status in WooCommerce (processing, completed, …) the customer is messaged on WhatsApp via Response360.
• Checkout opt-in consent. A consent checkbox at checkout captures the customer's permission to be messaged — so your WhatsApp/marketing sends stay compliant.
• Click-to-WhatsApp widget + shortcode. A floating chat button plus a [response360_whatsapp] shortcode/block so visitors can start a WhatsApp conversation from any page.
• Route your store's emails through Response360. A single toggle sends every WordPress email (order receipts, password resets, WooCommerce mails) through Response360 from your own verified domain — no separate SMTP plugin needed.

The email toggle bridges WordPress's wp_mail() to POST /v1/email, so mail is delivered on your DKIM-signed domain (better inbox placement) without any extra SMTP configuration.

For Shopify, Response360 ships a small self-hosted webhook relay (source in integrations/shopify). You host the relay, register it as a Shopify webhook endpoint, and it forwards store events to Response360.

It listens for orders/create, orders/paid, orders/fulfilled and abandoned-checkout events, verifies each with Shopify's HMAC signature, and forwards them to POST /v1/messages on your account.

Deploy the relay (it is zero-dependency Node), set your Response360 API key and Shopify webhook secret as environment variables, then add the relay URL as a webhook in your Shopify admin. If you prefer no hosting, you can wire the same events through Zapier instead.

orders/create · orders/paid · orders/fulfilled · abandoned-checkout
        │  (verify Shopify HMAC)
        ▼
POST https://api.response360.io/v1/messages   (Authorization: Bearer YOUR_API_KEY)

Zapier connects Response360 to 6,000+ apps with no code. Authenticate the Response360 Zapier app with an API key from your panel, then build Zaps.

Triggers (Response360 → Zapier): start a Zap when a message is received, answered by AI, escalated to a human, replied to by an agent, or on a delivery status change.

Action (Zapier → Response360): a Send-message action so any Zapier trigger (a new Shopify/BigCommerce order, a Google Sheet row, a form submission) can send a WhatsApp message through Response360.

This is the easiest path for platforms without a ready-made plugin — connect your store's Zapier app to the Response360 Send-message action.

For a custom platform (headless storefront, in-house backend, any stack) talk to the REST API directly. Every request is authenticated with your account's API key in the Authorization: Bearer header — no user login.

Base URL & auth

The API base is https://api.response360.io. Send your key as Authorization: Bearer YOUR_API_KEY on every request.

Test your key — GET /v1/me

A quick identity check to confirm your key works before wiring anything else:

curl https://api.response360.io/v1/me \
  -H "Authorization: Bearer YOUR_API_KEY"

WhatsApp — POST /v1/messages

Send a WhatsApp message. Two shapes: type:"text" (free-form, only inside the 24-hour reply window after the customer last messaged you) and type:"template" (a pre-approved template by name + language + variables). Templates are business-initiated and are how you send abandoned-cart, order-confirmation and shipping-update messages.

The WhatsApp rule, plainly: to message a customer outside the 24-hour window you must use a template. You author and submit templates for approval in the Response360 dashboard first, then reference the approved template by name in this API call. The recipient must have opted in — opted-out recipients are rejected (recipient_opted_out).

curl -X POST https://api.response360.io/v1/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+905551234567",
    "type": "text",
    "text": "Thanks! Your order is on the way."
  }'

curl -X POST https://api.response360.io/v1/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+905551234567",
    "type": "template",
    "template": "abandoned_cart",
    "language": "en",
    "variables": ["Alex", "3 items"]
  }'

Email — POST /v1/email

Send an email from your store's own verified domain (DKIM/SES). Pass "raw_html": true to send your own fully-formed HTML unchanged; omit it and Response360 wraps the body in a branded, unsubscribe-footered template. The same monthly quota, own-domain-only, and opt-out gates as the panel apply.

curl -X POST https://api.response360.io/v1/email \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "[email protected]",
    "subject": "Your order #1043 shipped",
    "body": "<h1>On its way!</h1><p>Track it here…</p>",
    "raw_html": true,
    "from_domain": "shop.example.com"
  }'

Outbound webhooks

Subscribe to events to keep your systems in sync. Response360 POSTs a signed JSON payload to your URL on each event, with an X-Response360-Signature HMAC-SHA256 header you verify with the signing secret (returned once when you create the webhook).

• message.receiveda customer sent you a message
• answered_by_aithe AI auto-answered from your content
• escalated_to_humanthe message was routed to an agent
• human.repliedan agent replied from the inbox
• delivery.statusan outbound message was delivered / read

Manage subscriptions from the panel (Integrations) or via POST /v1/webhooks. Always verify the signature before trusting a payload.