Managing Merchants

These endpoints operate on your partner account as a whole. They are authenticated with X-API-Key + X-API-Secret only — no merchant key. See Partner Authentication.

List connected merchants

curl "https://api.wava.co/v1/partners/stores" \
  -H "X-API-Key: YOUR_PARTNER_API_KEY" \
  -H "X-API-Secret: YOUR_PARTNER_SECRET_KEY"

{
  "stores": [
    {
      "id_store": 2841,
      "store_name": "Café Bogotá",
      "store_url": "https://cafebogota.co",
      "country": "Colombia",
      "currency": "COP",
      "status": "active",
      "integration_id": 5120,
      "integration_status": "active",
      "connected_at": "2026-08-06T14:22:30.000Z"
    }
  ],
  "total": 1
}

Only merchants with an active integration with your platform are returned. This is the authoritative answer to “who is connected to me” — use it to reconcile against the store_onboarded webhooks you have processed.

Merchant keys are not included here. They are delivered only in the store_onboarded webhook — see Onboarding Merchants.

Disconnect a merchant

curl -X POST "https://api.wava.co/v1/partners/stores/2841/deactivate" \
  -H "X-API-Key: YOUR_PARTNER_API_KEY" \
  -H "X-API-Secret: YOUR_PARTNER_SECRET_KEY"

{
  "success": true,
  "message": "Integration deactivated for store 2841"
}

This deactivates your integration on that merchant’s store. The merchant’s Wava account is unaffected — only the link to your platform is removed. The store disappears from GET /v1/partners/stores and its events stop reaching your webhook URL.

Response	Cause
`400` `INVALID_STORE_ID`	The path segment is not a positive integer
`404` `STORE_NOT_FOUND`	That store is not connected to your platform
`404` `INTEGRATION_NOT_FOUND`	The store is connected but has no active integration left to deactivate

Analytics

All analytics endpoints are scoped to the merchants connected to your platform. Every one of them accepts:

Query param	Default	Notes
`date_from`	30 days ago	`YYYY-MM-DD`
`date_to`	today	`YYYY-MM-DD`, must be on or after `date_from`
`currency`	`COP`	ISO 4217, exactly 3 characters
`timezone`	`-05:00`	Format `±HH:MM`

Endpoint	Returns
`GET /v1/partners/analytics/merchants`	Your merchants with their activity summary
`GET /v1/partners/analytics/summary`	Aggregated totals across all your merchants for the period
`GET /v1/partners/analytics/daily`	Day-by-day breakdown for the period
`GET /v1/partners/analytics/by-store`	Per-merchant performance. Extra param: `limit`
`GET /v1/partners/analytics/by-gateway`	Performance split by payment gateway, with gateway names resolved
`GET /v1/partners/analytics/orders`	Order list across your merchants. Extra params: `limit`, `offset`, `status` (`pending`, `confirmed`, `cancelled`, `refunded`), `gateway_id`, `store_id`
`GET /v1/partners/analytics/conversion-times`	Time-to-payment distribution

curl "https://api.wava.co/v1/partners/analytics/orders?date_from=2026-07-01&date_to=2026-07-31&status=confirmed&store_id=2841&limit=50" \
  -H "X-API-Key: YOUR_PARTNER_API_KEY" \
  -H "X-API-Secret: YOUR_PARTNER_SECRET_KEY"

store_id narrows results to a single merchant on /analytics/orders only. The other analytics endpoints always aggregate across every merchant connected to you.

Invalid query parameters return 400 with a validation error listing the offending fields.

Getting Started

Orders

Payment Flows

Payment Links

Partners

Webhooks

Integrations

Testing

Error Handling

Managing Merchants

Managing Merchants

List connected merchants

Disconnect a merchant

Analytics

​Managing Merchants

​List connected merchants

​Disconnect a merchant

​Analytics

Managing Merchants

List connected merchants

Disconnect a merchant

Analytics