Skip to content

Confirm manual flow setup

API v2 is in public beta: endpoints and fields can change before general availability. See the changelog

POST/account/integrations/{channel}/flows/confirm

Costs 2 rate-limit points · Rate limits

Record that the merchant set the flows up themselves: for Klaviyo (klaviyo_email, klaviyo_sms) the campaign type is switched to manual setup; for Postscript the template's flow is marked verified. Changes nothing in the provider.

Klaviyo takes campaign_type ("restock" default, or "preorder"); postscript takes template_id.

Also searched asi set up the klaviyo flow manuallymanual klaviyo setupconfirm postscript flow

Path parameters

  • channelstringRequired

    The integration channel whose flows to act on: klaviyo_email, klaviyo_sms or postscript.

Headers

  • Idempotency-Keystring

    A fresh unique key for every write (a new UUID, say); reuse it only to retry that write. Keys are remembered for 1 hour: the same key and the same request within that hour returns the first result, with Idempotent-Replayed: true, without running again; the same key with a different method, path or body is refused (422 idempotency_key_reused); a retry while the first is still running gets 409 idempotency_key_in_progress. Keys are per store. Server errors and rate limits are not kept, so their retry runs.

Request body

  • campaign_typestring

    Which alerts the flows are for, back in stock (restock, the default) or preorder.

    One of restockpreorder
    Default "restock"
  • template_idinteger

    Id of the notification template whose Postscript flow is marked verified; required for postscript.

Returns

  • channelstring
    Example: klaviyo_email
  • confirmedboolean
    Example: true
  • campaign_typestring
    Example: restock

Errors

404
not_found

The path is valid but nothing with that id exists in this store.

409
idempotency_key_in_progress

An earlier request with the same Idempotency-Key is still running. Wait, then resend the same request with the same key.

422
invalid_params

One or more fields failed the action's schema.

422
validation_failed

The request failed validation.

Any request can also fail with auth_invalid (401) or rate_limited (429).

Every error has the same shape: see Errors and the list of error codes.

POST/account/integrations/{channel}/flows/confirm
curl -X POST "https://app.stoqapp.com/api/v2/external/account/integrations/{channel}/flows/confirm" \
  -H "X-Auth-Token: $STOQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "campaign_type": "restock"
  }'
Response
{
  "channel": "klaviyo_email",
  "confirmed": true,
  "campaign_type": "restock"
}