zinn-campaigns

POST /v1/store-connect/support/tickets/{reference}/replies

The store owner replies to one of this store's tickets from the plugin.

All zinn-campaigns endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/store-connect/support/tickets/{reference}/replies \
  -H "Content-Type: application/json" \
  -d '{ "message": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Store token only. Another store's ticket is a 404. The ticket returns to open (waiting on support); a closed ticket is a 422 with code TICKET_CLOSED.

Parameters

NameTypeRequiredWhat it is
reference (path)stringYes—

Request body

NameTypeRequiredWhat it is
messagestringYes—

Response

NameTypeRequiredWhat it is
referencestringYes—
kindstring<help, bug, feedback, feature_request>Yes—
subjectstringYes—
statusstring<open, pending, solved, closed>Yes—
statestring<waiting_on_us, waiting_on_you, answered, closed>YesWhat the plugin shows (it translates the label).
created_atstringYes—
last_message_atobjectYes—
latest_replyobject | nullYesSupport's latest public reply, in the customer's language; null before one.

Errors this endpoint can return

401 · 404 · 422 · 429