Create subscription
This method will create a new subscription. You can provide an ID of an existing profile, or submit a full definition of a profile and security settings if you want to create new ones.
Authorizations:
Scopes:
path Parameters
channel required | string Enum: "BLOCKLIST" "CUSTOMER_ENGAGEMENT" "EMAIL" "FACEBOOK" "KAKAO_ALIM" "KAKAO_CHINGU" "LINE" "MMS" "MOBILE_IDENTITY" "MOBILE_PUSH" "NUMBER_LOOKUP" "OPEN_CHANNEL" "RCS" "REGISTRATION" "SMS" "VIBER" "VOICE_VIDEO" "WHATSAPP" "ZALO" Channel name. A separate subscription is needed for each channel. |
Request Body schema:
application/json- Blocklist
- Customer Engagement
- Kakao Alim
- Kakao Chingu
- Line
- MMS
- Mobile Identity
- Mobile Push
- Number Lookup
- Open Channel
- RCS
- Registration
- SMS
- Viber
- Voice and Video
- Zalo
Subscription group.
subscriptionId required | string [ 1 .. 255 ] characters Subscription ID. Used as part of a URL path and must not include any characters that require URL encoding. You cannot change the ID once a subscription is created. | ||||||||||||||||||||||||||||||||||||||||||||||||||
name | string [ 1 .. 255 ] characters A human-readable description for your subscription, can be changed at a later point. | ||||||||||||||||||||||||||||||||||||||||||||||||||
events required | Array of strings [ 0 .. 255 ] items Items Enum: "BLOCK" "UNBLOCK" List of events available for a subscription. Note that a set of events available for each channel is different; subscription to events that are unavailable for a certain channel will be ignored. For more details, see the availability table. In case you are configuring inbound Subscription please check all the details available here. | ||||||||||||||||||||||||||||||||||||||||||||||||||
criteria | Array of objects [ 0 .. 255 ] items Application and Entity pair to match. You can set the rule to match only Application or only Entity if necessary, omitting the other item. | ||||||||||||||||||||||||||||||||||||||||||||||||||
Array
| |||||||||||||||||||||||||||||||||||||||||||||||||||
resources | Array of strings [ 0 .. 255 ] items List of resources to match. At the moment, this could only be a sender name (whether numeric or alpha) used on message submit. | ||||||||||||||||||||||||||||||||||||||||||||||||||
users | Array of strings [ 0 .. 255 ] items List of users to match. You can provide usernames from your account. | ||||||||||||||||||||||||||||||||||||||||||||||||||
profile required | object Notification profile object holding the settings for your webhook URL and a reference to security settings. You can provide full definition of a notification profile and security settings if you want to create new items, or provide an ID of an existing profile to reuse it. If you want to reuse an existing profile, do not provide any other notification profile and security settings properties. | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Responses
Created.
Bad request.
Unauthorized
Forbidden
Not found.
Too many requests.
Internal Server Error
Request samples
- Payload
- cURL
- Java
- C#
- Go
- Python
- PHP
- JavaScript
- NodeJs
- Ruby
{- "subscriptionId": "ABC-123-DEF",
- "name": "Default group",
- "events": [
- "DELIVERY"
], - "criteria": [
- {
- "applicationId": "production",
- "entityId": "entity1"
}, - {
- "applicationId": "production",
- "entityId": "entity2"
}, - {
- "applicationId": "test",
- "entityId": "entity1"
}
], - "resources": [
- "1234"
], - "users": [
- "user1",
- "user2"
], - "profile": {
- "profileId": "NOTIF-32395",
- "security": {
- "authId": "NEWAUTH-9291",
- "type": "BASIC",
- "credentials": {
- "username": "user1",
- "password": "password1"
}
}
}
}
Response samples
- 201
- 400
- 401
- 403
- 404
- 429
- 500
{- "subscriptionId": "string",
- "profile": {
- "profileId": "string",
- "security": {
- "authId": "string"
}
}
}
Need assistance
Encountering issues
What's new? Check out
Unsure about a term? See