Server API Overview

About API

Our API is a REST API, which supports HTTP error codes to indicate API errors and use basic HTTP authentication to authenticate user’s account. All requests body must be in JSON format, we do not support other formats. However, we’re open-minded team and we are opened for any suggestions on formats or API logic. Please, write us support@gravitec.net if you have got any suggestions or issues with the API.

In addition to the REST API we provide to our clients WEB SDK API, which is essentially a JavaScript API designed to manage your subscriber’s database. For example, this SDK provides functions for tagging and setting aliases to your subscribers. Those tags and aliases could be useful for marketing purposes, such as – segmentation of subscribers’ database by their behavior or by their preferences.

Authentication

Authenticate your account when using the API by including your APP KEY and APP SECRET keys in the request. You can find your APP keys in the Site Settings page.

Your APP key allows to send push messages to all your subscribers database, so be careful and keep them in secret!

Authentication to the APP is performed via HTTP Basic Auth:

  • Provide your application key ("APP_KEY") as the basic AUTH username value
  • Provide your application secret ("APP_SECRET") as the basic AUTH password value
  • All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Code example:

// via shell
// example APP_KEY = 1e26f7bb3f81e1ab789d3e20b9cf6325
// example APP_SECRET = 9bb59fcbff38b85647c421c65cca06ce
curl -X \
  -u "1e26f7bb3f81e1ab789d3e20b9cf6325:9bb59fcbff38b85647c421c65cca06ce" \
  -H "Content-Type: application/json" \
  https://api.gravitec.net/api/v2/push.json

// or
curl -X \
  -u "1e26f7bb3f81e1ab789d3e20b9cf6325:9bb59fcbff38b85647c421c65cca06ce" \
  -H "Content-Type: application/json" \
  https://api.gravitec.net/api/v2/push.json

Send Push Notification V2

Definition

Method: POST

Endpoint: https://api.gravitec.net/api/v2/push.json

Headers: Content-Type: application/json

Request body:

{
 "send_date": "now",
 "message": "Push message text",
 "ttl": 3600,
 "chrome": {
   "header": "CHROME TITLE",
   "icon": "https://push.gravitec.net/img/gravitecBig.jpg",
   "redirect_url": "http://yoursite.com"
 },
 "audience": {
   "all": 1
 }
}
Arguments

send_date

Optional

default: "now"

type: String or Int

Date and time, when you want your push to be sent. For delayed push, you must set the desired date and time, which have to be in the future and for immediate sending set it to “now”.

NOTE: Time must be in UNIX_TIME format, which is essentially the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, minus the number of leap seconds that have taken place since then

Example:

"send_date": "now"   - immediate sending
"send_date": 1509058800 – send push at 2017.Oct.26 23:00:00

message

Required

type: String

Text, which will be displayed as push message text (pic. 2).

NOTE: Maximum length of the message is 240 symbols.

Example:

"send_date": "now"   - immediate sending
"send_date": 1509058800 – send push at 2017.Oct.26 23:00:00
doc-18.png

pic. 2

ttl

Optional

default: 3600

type: Int

The number of seconds that a message may be stored if the user is not immediately available.

NOTE: The number must be in between 0 and 2 419 200

NOTE: Keep in mind that a TTL value of 0 means messages that can't be delivered immediately to users are discarded. However, because such messages are never stored, this provides the best latency for sending notification messages

Example:

"ttl ": 14400   - time-to-live is set to 4 hours

chrome

Required

The “Chrome” section is required some arguments within the section are not required.

 

header

Optional

default: Title

type: String

Title or header of the message.

NOTE: Max length of header is 65 symbols

Example:

"header": "Just another header"

Chrome:

doc-19.png

Firefox:

doc-20.png

icon

Required

type: String

URL of the notification's icon. Sets the notification icon to specified image URL. Image must be at least 80x80 pixels and with 1:1 ratio. The pictures without that ratio will be resized and probably distorted.

NOTE: Provide correct URL, without spaces or tabs at the start and at the end of the URL and with ending .jpg, .jpeg or .png, otherwise the error will be fired.

NOTE: Maximum length of the URL is 1000 symbols.

NOTE: Providing “icon": “” will set the icon to default site icon, which can be set in the Site Settings page.

Example:

"icon": "https://push.gravitec.net/img/gravitecBig.jpg
doc-21.png

redirect_url

Required

type: String

URL, which will be opened in user’s browser if user clicks on the notification.

NOTE: Maximum length of the URL is 1000 symbols.

NOTE: Provide correct URL, without spaces or tabs at the start and at the end of the URL, otherwise the error will be fired.

Example:

"redirect_url": "http://yoursite.com/news"

audience

Required

The “Audience” section is required. The section must contain only one of these variables: alltokensaliases or tags.

 

all

Optional

type: Int

Setting this parameter in any value means that message will be send to all subscribers.

NOTE: Any JSON correct value is accepted, but we would recommend you to set it in 1, as mentioned in example.

Example (of the whole Audience section):

"audience": {
  "all": 1
}

tokens

Optional

type: Array

Specifying a list of subscribers’ IDs in this parameter means that message will be send exactly to the list of subscribers specified. You can get subscriber’s ID by using getSubscription function from our Web SDK API

NOTE: Array size is limited to 100 IDs.

Example:

"tokens": ["dec301908b9ba...8df85e57a58e40f96f", "523f4c2068674f1fe...2ba25cdc250a2a41"]

aliases

Optional

type: Array

Specifying a list of aliases means that message will be sent exactly to the list of subscribers who are associated with aliases provided in the list. You can set an alias by using setAlias function from our Web SDK API.

Example:

"aliases": ["own_id_device_1", "own_id_device_2", "own_id_device_3"]

tags

Optional

type: Array

Specifying a list of tags means that message will be send exactly to the list of subscribers who were tagged with tags provided in the list. You can tag your subscribers by using addTag or setTags function from our Web SDK API

Example:

"tags": ["tag1", "tag2", "tag3"]
Examples

Send push to all followers of site

curl -X POST \
-H "Content-Type: application/json" \
-u "APP_KEY:APP_SECRET" \
--data '{
  "message": "Push message",
  "chrome": {
    header": "title message",
    icon": "http://example.com/icon.png",
    redirect_url": "http://yoursite.com/new"
  },
  "audience": {
    "all": 1
  }
}' \
https://api.gravitec.net/api/v2/push.json

Send push to followers of site who were tagged with tag1 and tag2

curl -X POST \
-H "Content-Type: application/json" \
-u "APP_KEY:APP_SECRET" \
--data '{
  "message": "Push message",
  "chrome": {
    "header": "title message",
    "icon": "http://example.com/icon.png",
    "redirect_url": "http://yoursite.com/new"
  },
  "audience": {
    "tags": ["tag1", "tag2"]
  }
}' \
https://api.gravitec.net/api/v2/push.json
Responses (Results and Errors)

200 OK - Standard response for successful HTTP requests

Request

{
  "send_date":"now",
  "message":"Push message text",
  "ttl":3600,
  "chrome": {
    "header":"CHROME TITLE",
    "icon": "https://push.gravitec.net/img/gravitecBig.jpg",
    "redirect_url": "http://yoursite.coma"
  },
  "audience": {
    "all": 1
  }
}

Response

{
  "id": "1578964386674900992",
  "status": "completed",
  "message": "Push message text",
  "title": "CHROME TITLE",
  "platforms": "chrome",
  "ttl": "3600",
  "date": "Tue Sep 19 13:43:02 EEST 2017"
}

403 FORBIDDEN - authorization failed

Request

POST /api/v2/push.json HTTP/1.1

Host: api.gravitec.net

Content-Type: application/json

Authorization: Basic NTQ1OTA1OTA1OTQwNTk0MGdwZ2tqOmVyZmdkZmdkZmdkZmc=

Cache-Control: no-cache

{
  "send_date": "now",
  "message": "Push message text",
  "ttl": 3600,
  "chrome": {
    "header": "CHROME TITLE",
    "icon": "https://push.gravitec.net/img/gravitecBig.jpg",
    "redirect_url": "http://yoursite.coma"
  },
  "audience": {
    "tags": ["tag1", "tag2", "tag3"]
  }
}

Response

{
  "status": "incomplete by bad auth",
  "error_message": "There is no web site with appKey: 5459059059405940gpgkj"
}

404 NOT FOUND - missed required parameter

Request

{
  "send_date": "now",
  "message": "Push message text",
  "ttl": 3600,
  "chrome": {
    "header": "CHROME TITLE",
    "icon": "https://push.gravitec.net/img/gravitecBig.jpg",
    "redirect_url": "http://yoursite.coma"
  }
}

Response

{
 "status": "incomplete by missed req param(s)",
 "error_message": "Audience required"
}

412 PRECONDITION_FAILED - bad message

Request

{
  "message": "Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test message$Test Test message$Test message$Test message$Test message$Test message$Test test",
  "chrome": {
   "header": "Test it out!",
   "icon": "https://cdn.gravitec.net/img/logo_footer.png",
   "redirect_url": "https://gravitec.net/"
   "all": 1
  },
  "send_date": "now"
}

Response

{
 "status": "incomplete by wrong param(s)",
 "error_message": "message max length is 1000 symbol"
}

417 EXPECTATION_FAILED - wrong parameter

Request

{
  "send_date": "2017-09-20",
  "message": "Push message text",
  "ttl":3600,
  "chrome": {
    "header": "CHROME TITLE",
    "icon": "https://push.gravitec.net/img/gravitecBig.jpg",
    "redirect_url": "http://yoursite.coma"
  },
  "audience": {
    "all": 1
  }
}

Response

{
  "status": "incomplete by wrong param(s)",
  "error_message": "date must be timestamp or now"
}

424 FAILED_DEPENDENCY - bad audience

Request

{
  "send_date": "now",
  "message": "Push message text",
  "ttl": 3600,
  "chrome": {
    "header":"CHROME TITLE",
    "icon": "https://push.gravitec.net/img/gravitecBig.jpg",
    "redirect_url": "http://yoursite.coma"
  },
  "audience": {
    "tags": ["tag1", "tag2", "tag3"]
  }
}

Response

{
  "status": "incomplete by bad audience",
  "error_message": "tags list is invalid"
}

Send Push Notification V3

Set alias for subscriber V3

Definition

Method: POST

Endpoint: https://uapi.gravitec.net/api/v3/alias

Request parameters:

  • regId - subscriber’s token [Required, 1-255 symbols string]
  • name - desired alias name [Required, 1-255 symbols string]

NOTE: All request parameters names and values are case-sensitive.

Request URL example:

https://uapi.gravitec.net/api/v3/alias?regId=someregid&name=newalias
Responses

200 OK

The alias was successfully added

400 Required String parameter "name" is not present

"name" parameter was not provided in request

400 Required String parameter "regId" is not present

"regId" parameter was not provided in request

422 Unprocessable Entity

No follower with regID provided was found

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "There is no follower with this regId!"
}

422 Unprocessable Entity

Provided alias name length was more than 255 symbols

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "Max alias length is 255!"
}


Set Tag for subscriber V3

Definition

Method: POST

Endpoint: https://uapi.gravitec.net/api/v3/tag

Request parameters:

  • regId - subscriber’s token [Required, 1-255 symbols string]
  • name - desired tag name [Required, 1-255 symbols string]

NOTE: All request parameters names and values are case-sensitive.

NOTE: Tags saving method behaves with case sensitive values like:

First tag will be saved in exact case it provided, if another tag, which in case-insensitive comparison is the same one, provided, it will not be added as a new tag – the system considers it as the same as previous.

Request URL example:

https://uapi.gravitec.net/api/v3/tag?regId=someregid&name=tagname
Responses

200 OK

Tag was successfully added

400 Required String parameter "name" is not present

"name" parameter was not provided in request

400 Required String parameter "regId" is not present

"regId" parameter was not provided in request

422 Unprocessable Entity

No follower with regID provided was found

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "There is no follower with this regId!"
}

422 Unprocessable Entity

Provided tag name length was more than 255 symbols

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "Max alias length is 255!"
}

Delete subscriber’s tag V3

Definition

Method: DELETE

Endpoint: https://uapi.gravitec.net/api/v3/tag

Request parameters:

  • regId - subscriber’s token [Required, 1-255 symbols string]
  • name - desired tag name [Required, 1-255 symbols string]

NOTE: All request parameters names and values are case-sensitive.

Request URL example:

https://uapi.gravitec.net/api/v3/tag?regId=someregid&name=tagname
Responses

200 OK

Tag was successfully deleted

400 Required String parameter "name" is not present

"name" parameter was not provided in request

400 Required String parameter "regId" is not present

"regId" parameter was not provided in request

422 Unprocessable Entity

No follower with regID provided was found

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "There is no follower with this regId!"
}

422 Unprocessable Entity

Provided tag was not found for the subscriber with provided regId.

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "The follower doesn't have this tag!"
}

422 Unprocessable Entity

Provided tag name length was more than 255 symbols

Body:

{
  "httpStatus": "UNPROCESSABLE_ENTITY",
  "error": "Incomplete by wrong param(s)!",
  "errorDescription": "Max alias length is 255!"
}

Get subscriber’s alias V3

Definition

Method: GET

Endpoint: https://uapi.gravitec.net/api/v3/alias

Request parameters:

  • regId - subscriber’s token [Required, 1-255 symbols string]

NOTE: All request parameters names and values are case-sensitive.

Request URL example:

https://uapi.gravitec.net/api/v3/alias?regId=someregid
Responses

regIdExists [boolean]

  • Is "true" if provided in request regId is an actual subscriber’s token
  • Set in "false" if provided in request regId does not exists as actual subscriber’s token

aliasExists [boolean]

  • Is "true" if provided in request regId is an actual subscriber’s token and there is an active alias for that token
  • Is "false" if provided in request regId is an actual subscriber’s token and there is no active alias for that regID
  • Does not present in response if regIdExists is "false"

isActiveFollower [boolean]

  • Is "true" if provided in request regId is a token of an active subscriber
  • Is "false" if provided in request regId is a token of an inactive subscriber
  • Does not present in response if regIdExists is "false"

alias [string]

  • Is an actual and active alias for provided in request regId
  • Does not present in response if regIdExists is "false"

200 - OK

400 - Required String parameter regId is not present

 
Examples

RegId property was not in request

Request:

https://uapi.gravitec.net/api/v3/alias?regId=

Response code:

400 - Required String parameter regId is not present

RegId exists as actual subscriber’s token

Request:

https://uapi.gravitec.net/api/v3/alias?regId=okf8kj589ktGF5g3gF#gf3#46g^^6gfGfgfgfg%g5g

Response code:

200 - OK

Response body:

{
  "regIdExists": "false"
}

There is no active alias for regID

Request:

https://uapi.gravitec.net/api/v3/alias?regId=okf8kj589ktGF5g3gF#gf3#46g^^6gfGfgfgfg%g5g

Response code:

200 - OK

Response body:

{
  "regIdExists": "true",
  "aliasExists": "false",
  "isActiveFollower": "true"
}

There is an active alias for regID and subscriber is not in an active state

Request:

https://uapi.gravitec.net/api/v3/alias?regId=okf8kj589ktGF5g3gF#gf3#46g^^6gfGfgfgfg%g5g

Response code:

200 - OK

Response body:

{
  "regIdExists": "true",
  "aliasExists": "true",
  "isActiveFollower": "false",
  "alias": "alias1"
}

There is an active alias for regID and subscriber is in an active state

Request:

https://uapi.gravitec.net/api/v3/alias?regId=okf8kj589ktGF5g3gF#gf3#46g^^6gfGfgfgfg%g5g

Response code:

200 - OK

Response body:

{
  "regIdExists": "true",
  "aliasExists": "true",
  "isActiveFollower": "true",
  "alias": "alias1"
}
Send Push Notification V3

Definition

Method: POST

Endpoint: https://uapi.gravitec.net/api/v3/push

Headers: Content-Type: application/json

Request body properties:

{
  "send_date":"",
  "ttl":"",
  "display_time": "",
	"is_transactional":"",
  "payload": {
    "message":"",
    "title":"",
    "icon":"",
    "image":"",
    "redirect_url":"",
    "buttons": [{
      "title":"",
      "url":""
    }]
  },
  "audience": {
    "tokens":[""],
    "aliases":[""],
    "tags":[""]
  }
}
Properties

send_date

Optional

default: ""

type: String or Int

Date and time, when you want your push to be sent. For delayed push, you must set the desired date and time, which have to be in the future and for immediate sending set it to "now".

NOTE: Time must be in UNIX_TIME format, which is essentially the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, minus the number of leap seconds that have taken place since then

Example:

"send_date": "" - immediate sending
"send_date": 1509058800 – send push at 2017.Oct.26 23:00:00

ttl

Optional

default: 28800

type: Int

The number of seconds that a message may be stored if the user is not immediately available.

NOTE: The number must be in between 0 and 2 419 200

NOTE: Keep in mind that a TTL value of 0 means messages that can't be delivered immediately to users are discarded. However, because such messages are never stored, this provides the best latency for sending notification messages

Example:

"ttl ": 28800   - time-to-live is set to 8 hours

display_time

Optional

default: 60

type: Int

The number of seconds that a message will be displayed on participant’s screen

NOTE: If set in 0 – the message will be displayed until user clicks on it

NOTE: Maximum time is 2419200

 

is_transactional

Optional

default: false

type: boolean

Marks a push message as Transactional, thus the message will not be displayed in the main campaign history section of the web application (https://push.gravitec.net). Use this if you send a great deal of small messages, which are by itself contains transactional data like personal notifications for your users, reminders, etc.

NOTE: If omitted, false" value will be set for a push message

 

payload

Required

The "Payload" section is required, whereas some arguments within the section are not required.

 

message

Required

type: String

Text, which will be displayed as push message text

NOTE: Maximum length of the message is 1000 symbols.

Example:

"message": "Push message text"
doc-18.png

title

Optional

default: Title

type: String

Title or header of the message.

NOTE: Max length of title is 1000 symbols.

Example:

"header ": "Just another header"

Chrome:

doc-19.png

Firefox:

doc-20.png

icon

Required

type: String

URL of notification's icon. Sets the notification icon to specified image URL. Image must be at least 80x80 pixels and with 1:1 ratio. Pictures without that ratio will be resized with its aspect ratio and put on a white square.

NOTE: Provide correct URL, without spaces or tabs at the start and at the end of the URL and with ending .jpg, .jpeg or .png, otherwise the error will be fired.

NOTE: Maximum length of the URL is 1000 symbols.

NOTE: Providing "icon": "" will set the icon to default site icon, which can be set in the Site Settings page

Example:

"icon": "https://push.gravitec.net/img/gravitecBig.jpg"

1:1 aspect ratio and more than 80x80 on X and Y sides:

doc-21.png

1:1.2 aspect ratio and more than 80 on Y side:

doc-22.png

1.2:1 aspect ratio and more than 80 on X side:

doc-23.png

Less than 80x80 on X and Y sides:

doc-24.png

image

Optional

type: String

URL of big picture to display below the notification main body. For the best results provided image must be with 1.5:1 sides ratio and size at least 360x240 pixels.

NOTE: Provide correct URL, without spaces or tabs at the start and at the end of the URL and with ending .jpg, .jpeg or .png, otherwise the error will be fired

NOTE: Maximum length of the URL is 1000 symbols.

NOTE: Pictures, which are not in 1.5:1 ratio or less then 360x240 and will be resized according to their aspect ratio and put on top of a white image of 360x240 px

Different image processing examples:

1.5:1 aspect ratio and more or equal than 360x240 on X and Y sides accordingly:

doc-25.png

1:1.2 aspect ratio and more than 240 on Y side:

doc-26.png

1.2:1 aspect ratio and more than 360 on X side:

doc-27.png

Less than 360x240 on X and Y sides:

doc-28.png

redirect_url

Required

type: String

URL which will be opened in user’s browser if user clicks on the notification.

NOTE: Maximum length of the URL is 1000 symbols.

NOTE: Provide correct URL, without spaces or tabs at the start and at the end of the URL, otherwise the error will be fired.

Example:

"redirect_url": "http://yoursite.com/news"

buttons

Optional

Specify in this array one or two action buttons, which will be displayed below the notification main body:

Example:

doc-29.pngdoc-30.png

title

Required

type: String

Provide appropriate title for the button.

NOTE: Max length of title is 48 symbols

 

url

Required

type: String

URL which will be opened in user’s browser if user clicks on the notification.

NOTE: Maximum length of the URL is 1000 symbols.

NOTE: Provide correct URL, without spaces or tabs at the start and at the end of the URL (rfc3986)

 

audience

Optional

The "Audience" section is optional.

NOTE: If omitted, the system shall send push message to all subscribers.

NOTE: If set - the section must contain only one of these variables (in other case, error will be fired):

 

tokens

Optional

type: Array

Specifying a list of subscribers’ IDs in this parameter means that message will be send exactly to the list of subscribers specified. You can get subscriber’s ID by using getSubscription function from our Web SDK API.

NOTE: Array size is limited to 100 IDs.

Example:

"tokens": ["dec301908b9ba...8df85e57a58e40f96f", "523f4c2068674f1fe...2ba25cdc250a2a41"]

aliases

Optional

type: Array

Specifying a list of aliases means that message will be sent exactly to the list of subscribers who are associated with aliases provided in the list. You can set an alias by using setAlias function from our Web SDK API.

Example:

"aliases": ["own_id_device_1", "own_id_device_2", "own_id_device_3"]

tags

Optional

type: Array

Specifying a list of tags means that message will be send exactly to the list of subscribers who were tagged with tags provided in the list. You can tag your subscribers by using addTag or setTags function from our Web SDK API.

Example:

"tags": ["tag1", "tag2", "tag3"]
Responses (Results and Errors)

200 OK - Standard response for successful HTTP requests

Request

{
  "payload": {
    "message": " Test massage",
    "title": "Test message",
    "redirect_url": "https://gravitec.net"
  }
}

Response

{
  "id": "1590394828308348928",
  "send_date": "1516718700678",
  "ttl": 86400,
  "display_time": 60,
  "payload": {
    "title": "Test message"
  }
}

403 FORBIDDEN - authorization failed

Request

POST /api/v3/push HTTP/1.1
Host: api.gravitec.net
Content-Type: application/json
Authorization: Basic Z2hqZ2hqZ2g6aGdtamdoag==
Cache-Control: no-cache

{
  "payload": {
    "message": "Test massage",
    "title": "Test message",
    "redirect_url": "https://gravitec.net"
  }
}

Response

{
  "status": "incomplete by bad auth",
  "error_message": "There is no web site with appKey: 5459059059405940gpgkj"
}
Get push Notification stats

Definition

Method: GET

Endpoint: https://uapi.gravitec.net/api/v3/messages/

Request parameters:

  • campaignID - Campaign ID [Required, Id from “Send Push Notification V3]

NOTE: All request parameters names and values are case-sensitive.

Request URL example:

https://uapi.gravitec.net/api/v3/messages/1603861504654835713
Responses

200 OK

The alias was successfully added

400 Required parameter "campaignID" is not present

"campaignID" parameter was not provided in request

422 Unprocessable Entity

No Push Campaign with campaignID provided was found

Body:

{
"httpStatus": "UNPROCESSABLE_ENTITY", 
"error": "Incomplete by wrong param(s)!", 
"errorDescription": "There is no message with this id!"
}