Skip to content
Reponse.ai LogoDocs
DocsAPISDKsGuides

Search Documentation

Search for an article...

Getting Started

  • Overview
  • Architecture
  • Installation
  • Authentication
  • First Request

Products & Collections

  • Products — List
  • Products — Get
  • Products — Metafields
  • Collections — List
  • Collections — Get
  • Collections — Products

Cart & Checkout

  • Cart — Create
  • Cart — Get
  • Cart — Add Item
  • Cart — Update Item
  • Cart — Remove Item
  • Cart — Apply Promotion
  • Checkout — Stripe
  • Checkout — Payment Intent
  • Checkout — ACP

Orders & Fulfillment

  • Orders — Create
  • Orders — Get
  • Orders — Confirm
  • Orders — Cancel
  • Orders — Fulfill
  • Orders — Refund

Commerce

  • Inventory — Get
  • Inventory — Update
  • Shipping — Rates
  • Discounts — List
  • Discounts — Create
  • Discounts — Validate
  • Subscriptions — Manage

Loyalty & Gift Cards

  • Loyalty — Balance
  • Loyalty — Redeem
  • Loyalty — Referral
  • Gift Cards — List
  • Gift Cards — Redeem

Tickets & Support

  • Tickets — List
  • Tickets — Create
  • Tickets — Reply

Platform

  • Product Feed — JSON
  • Product Feed — CSV
  • Theme — Get
  • Approvals — Execute
  • Approvals — Reject
  • Geocode

SDKs

  • SDK Overview
  • TypeScript SDK
  • React Hooks

Guides

  • Chat Widget
  • Shopify Sync
  • Storefront Starter
  • Loyalty Program
  • Discounts & Promotions
  • Subscriptions
  • Klaviyo Integration
  • Custom Domains
  • Agentic Commerce (ACP)
  • A2A Protocol
  • AI Engines
  • MCP Server

Webhooks

  • Webhooks Overview
  • Events Reference
  • Shopify Webhooks
  • Stripe Webhooks
  • Reviews (Stamped / Trustpilot)
  • Logistics
  • Email Inbound

Resources

  • Environment Variables
  • Rate Limits
  • Changelog
DocsGetting StartedArchitecture

Architecture

How the Reponse platform is structured.

1 min read/Last updated Aug 19, 2026
On this page

Overview

Reponse is built on a Next.js application backed by Supabase (Postgres). The REST API under `/v1` is the single integration surface; the TypeScript SDK is generated from the same OpenAPI specification, so the SDK and the API never drift apart.

Platform Architecture

graph TD subgraph Clients A[TypeScript SDK] B[React Hooks] C[MCP Server] D[Storefront Starter] end subgraph API Layer E["/v1 REST API"] F["AI Activation Layer"] end subgraph Core G["Supabase (Postgres)"] H["Auth & Workspace Scoping"] end subgraph External I[Shopify] J[Stripe / Paddle] K[Klaviyo] L[Logistics Providers] end A -->|HTTP| E B -->|HTTP| E C -->|Tools| E D -->|HTTP| E F -->|Orchestrates| E E -->|Read/Write| G E -->|Validates| H H -->|Scopes| G I -->|Webhooks| E J -->|Webhooks| E K -->|Events| E L -->|Webhooks| E

Layers

Data lives in Supabase. The `/v1` API exposes it with workspace-scoped authentication. The SDK and React hooks wrap the API. The AI activation layer and MCP server sit on top.

LayerRoleExamples
DataPostgres via SupabaseProducts, orders, carts, conversations
APIREST endpoints under /v1GET /v1/products, POST /v1/carts
SDKTypeScript client + React hooks@reponse/sdk, useProducts()
AIActivation layer + MCP serverEngine selection, intent classification
IntegrationsExternal service syncShopify, Stripe, Klaviyo, logistics

Request Flow

sequenceDiagram participant Client participant API as /v1 API participant Auth as Auth Layer participant DB as Supabase Client->>API: Request + Bearer API key API->>Auth: Validate key Auth-->>API: Workspace ID API->>DB: Query (scoped to workspace) DB-->>API: Data API-->>Client: JSON response

Multi-tenancy

Every resource is scoped to a workspace. Your API key determines the workspace, and the API enforces it on every query. There is no cross-workspace data access — isolation is enforced at the database level.

PreviousOverview
NextInstallation