Development guide
Prev | Chapter 2. REST API |

## Development guide

### Warning

THIS IS FOR INTERNAL USE ONLY!!

### Push Notification format

#### FcmXmppApiProvider

This provider sends APNs notifications using following fields and values.

Field | Value | Description
message_id | "m-" + UUID | Random id for the notification
priority | high | Priority of the notification
data | Description of fields used within "data" object
Field | Value | Description
--- | --- | ---
account | user@example.com | Bare JID of user account
unread-messages | 2 | Number of unread messages waiting
sender | sender@example.com/test | Full JID of a sender of the last message
body | "Text of a message body" | Text of a message body limited to 500 chars with ellipsis added if message body exceeds 512 chars

### Note

Any of fields described above may be not passed if notification sent to PUSH provider does not contain values for a particular fields.

#### APNsBinaryApiProvider

This provider sends APNs notifications using following fields and values.

Field | Value | Description
action-loc-key | "Show" | Name of action
content-available | 1 | Mark notification as there is a content waiting for download (ie. XMPP message to retrieve)
account | user@example.com | Bare JID of user account
unread-messages | 2 | Number of unread messages waiting
sender | sender@example.com/test | Full JID of a sender of the last message
body | "Text of a message body" | Text of a message body limited to 500 chars with ellipsis added if message body exceeds 512 chars

### Note

Any of fields described above may be not passed if notification sent to PUSH provider does not contain values for a particular fields.

Prev | Up |
BOSH HTTP Pre-Binding | Home |