No-code docs

Compliance Keywords Messages

SMS Compliance keywords messages endpoints allow you to manage answers that are sent to compliance keywords (as STOP for unsubscription )

Compliance Keyword messages are only available for SMS

Types of KeyWords (KW field)

In order to set customized compliance keyword messages you will need to associate them with a type of keyword ( kw ) . Several types exist 

type: string
enum:
  - "optin"
  - "optout"
  - "help"

OPT IN

Categories all keywords that indicate a subscriber's intention to subscribe or resubscribe to a service (ex START)

OPT-OUT

Categories all keywords that indicate a subscriber's intention to unsubscribe from a service (ex STOP)

HELP

Categories all keywords intended to provide simplified instructions to subscribers (ex HELP) .

Good practices require structuring HELP messages as follows

brand_name , support_contact (both URL or TFN or email ) followed by common_keywords . For example:

Bird CRM: you can contact us at support@bird.com, send START to subscribe, STOP to unsbscribe. Msg & data charges may applies

Languages

Compliance Keywords Messages are always associated with the language; so for example. optin:en Identify all keywords in English ( en ) that are used to identify a contact opting in to receive communications from a brand

When the filed lang Is required, please specify a language using ISO639-1 language codes

Default Keywords

Bird CRM system always listens for predetermined keywords categorized by type and language as below. Via the Compliance Keywords Messages endpoint you can customize the acknowledgment message each category will trigger.

English

HELP

  • help

  • info

OPT OUT

  • stop

  • stopall

  • end

  • quit

  • cancel

  • unsubscribe

OPT IN

  • start

  • begin

  • resume

  • revert

  • unstop

Other languages

HELP

  • aide (french)

  • hulp (dutch)

  • hilfe (german)

  • ayuda (spanish)

  • ajuda (portuguese)

  • Aiuto (italian)

  • ПОМОЩЬ (russian)

  • POMOCY (polish)

OPT OUT

  • arret (french)

  • halt (german)

  • detener (spanish)

  • parar (pourtugese)

  • ferma (italian)

  • ОСТАНОВИТЬ (russian)

  • ZATRZYMAJ (polish)

OPT IN

  • nonarret (french)

Endpoints

List all messages

List all keyword messages

get

List all keyword messages for this workspace

Authorizations
Path parameters
workspaceIdstring · uuidRequired

The ID of the workspace

Responses
200
OK
application/json
Responseall of
get
GET /workspaces/{workspaceId}/keyword-messages HTTP/1.1
Host: 
Authorization: Bearer jwt
Accept: */*

{
  "results": [
    {
      "Key": "text",
      "KW": "optin",
      "Lang": "text",
      "Value": "text"
    }
  ]
}

This endpoint will return all the costume messages you have set in the target workspace 

{
	"results": [
		{
			"key": "optout:en",
			"kw": "optout",
			"lang": "en",
			"value": "We are sorry to see you go, please send OOPS if that was a mistake"
		}
}

Define a message for a given keyword

Set keyword message

post

Set a keyword message

Authorizations
Path parameters
workspaceIdstring · uuidRequired

The ID of the workspace

Body
kwstring · enumRequiredPossible values:
langstringRequired
valuestringRequired
Responses
200
Keyword message was created
post
POST /workspaces/{workspaceId}/keyword-messages HTTP/1.1
Host: 
Authorization: Bearer jwt
Content-Type: application/json
Accept: */*
Content-Length: 43

{
  "kw": "optin",
  "lang": "text",
  "value": "text"
}
No content
{
    "kw":    "optout",
    "lang":  "en",
    "value": "We are sorry to see you go, please send OOPS if that was a mistake",
}

You can only define a message for a type of keyword and language (keywordMessageKey ). You cannot have multiple messages for the same combination of type and language

If you want to revert to the default message, use the below methods with an empty value "value": ""

Check a Singel Compliance Keyword Message

Get keyword message

get

Get keyword messages for this workspace and key (keyword:lang)

Authorizations
Path parameters
workspaceIdstring · uuidRequired

The ID of the workspace

keywordMessageKeystringRequired
Responses
200
OK
application/json
Responseall of
get
GET /workspaces/{workspaceId}/keyword-messages/{keywordMessageKey} HTTP/1.1
Host: 
Authorization: Bearer jwt
Accept: */*

{
  "Key": "text",
  "KW": "optin",
  "Lang": "text",
  "Value": "text"
}

keywordMessageKey indicates the keyword type and languages, for example for the example above it would be optout:en

Last updated

Was this helpful?