Remove follow-up template
Overview
Clear the follow-up email template association on a campaign channel by setting its follow_up_template_id to null. The channel is looked up by its unique_code. If not found the endpoint returns 400. If the channel's store company does not belong to the authenticated user the endpoint returns 403.
Prerequisites
- A bearer token. Callable with Account tokens.
- The
uniqueCodeof the record you are targeting.
Base URL
| Environment | URL |
|---|---|
| Production | https://production-api.shoutaboutus.com |
| Development | https://development-api.shoutaboutus.com |
Endpoint
DELETE /api/v1/campaign/channel/{uniqueCode}/remove/followup
Authentication
-
Requires a bearer token in the
Authorization: Bearer <bearer-token>header. -
Who can call it: Account tokens.
-
Authentication.
-
The endpoint resolves the channel by
unique_code. This matches the user'sperson.company_idagainst the channel's store-company id or up to two parent companies (location, then account, then partner) in the company tree. -
Lives in the account-operated
campaignroute group.
Rate limit
- No rate limit.
Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
uniqueCode | string | Required | The channel's unique code, not a numeric campaign id. |
Response
data.message(string) — confirmation text"Follow up template removed successfully".
200 OK · 200
200{ "data": { "message": "Follow up template removed successfully" } }Errors
| Status | Meaning |
|---|---|
400 | The request was rejected — the response explains why |
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Example request
curl --request DELETE \
--url "https://production-api.shoutaboutus.com/api/v1/campaign/channel/<uniqueCode>/remove/followup" \
--header 'Authorization: Bearer <bearer-token>' \
--header 'Accept: application/json'Updated 11 days ago
