{"_id":"593878f4682adc0031784c09","category":{"_id":"593878f2682adc0031784bf5","version":"593878f2682adc0031784bf3","project":"55f0757d4624ec2d00814345","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-09T21:17:41.905Z","from_sync":false,"order":1,"slug":"tigerconnect-basics","title":"Basics"},"parentDoc":null,"project":"55f0757d4624ec2d00814345","user":"55f0756a1e63fc37004b8d2b","version":{"_id":"593878f2682adc0031784bf3","project":"55f0757d4624ec2d00814345","__v":1,"createdAt":"2017-06-07T22:06:42.610Z","releaseDate":"2017-06-07T22:06:42.610Z","categories":["593878f2682adc0031784bf4","593878f2682adc0031784bf5","593878f2682adc0031784bf6","593878f2682adc0031784bf7","593878f2682adc0031784bf8","593878f2682adc0031784bf9","593878f2682adc0031784bfa","593878f2682adc0031784bfb"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.0.0","version":"3"},"__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-11-13T23:42:40.404Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Message Delivery Status\"\n}\n[/block]\nEach message has a particular delivery status that provides information to the sender on whether the recipients have successfully read the message.  \n\nMessage delivery has 3 distinct states:\n\n1.  **Sent** - the message has been successfully sent to the TigerText platform\n\n2.  **Delivered** - the message has been downloaded by the recipient's device but has not yet been read.  \n\n3.  **Read** - the message has been read by the recipient\n\nFor each message sent, the server will provide updates on the delivery status on the event stream which is described in the [Events](doc:events-2) section.  For group messages, the message delivery status is captured for each recipient. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Time To Live (TTL)\"\n}\n[/block]\nEach message has a Time To Live (TTL).  This can range from a few seconds when Delete on Read (DOR) is activated or up to 30 days.  Once the message exceeds its TTL, the message will self destruct and be removed from the platform.  \n\nWhile each message can have separate TTLs, the lifespan can also be managed at the [Organization](doc:organizations) level.  In the case the [Organization](doc:organizations) has the lifespan set, the message lifespan will be adjusted to the lower of the two lifespan settings. \n\nEach client is responsible for managing and adhering to lifespan settings indicated by the platform.  It is important for security purposes to continue to delete messages once expired.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Message Recall and Delete\"\n}\n[/block]\nMessages can be recalled by the message sender.  When a message is successfully recalled, the message will no longer exist on both the sender and receiver clients.  \n\nKeep in mind, a [User](doc:messaging-users-and-groups) is unable to recall messages that they did not send.  However, the receiver can delete the message from their client.  Note: deleting a message does not remove the message from the Sender's clients.  \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Attachments\"\n}\n[/block]\nMessages can contain various attachments which are similarly secured and encrypted both at rest and in transit.  Similarly, attachments are marked with a Time To Live and can be recalled by the sender.\n\nCurrently the platform supports attachments up to 10MB in size for the several data file types including the following: \n\n**Images: **\n-  JPEG (.jpg) \n-  PNG (.png)\n-  GIF (.gif)\n\n**Documents**\n-  Adobe (.pdf)\n-  Word (.doc, .docx) \n-  Excel (.xls, .xlsx)\n-  Powerpoint (.ppt, .pptx) \n\n**Audio / Video**\n-  MediaPlayer (.mov, .mp4, m4v) \n-  MP3 (.mp3)\n-  Waveform (.wav)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Message Token\"\n}\n[/block]\nEach message has a unique message token.  You are able to use the token to get information about a message.  See the [/message/:message](doc:messagemessage-id)] documentation for an example.","excerpt":"","slug":"messages","type":"basic","title":"Messages"}
[block:api-header] { "type": "basic", "title": "Message Delivery Status" } [/block] Each message has a particular delivery status that provides information to the sender on whether the recipients have successfully read the message. Message delivery has 3 distinct states: 1. **Sent** - the message has been successfully sent to the TigerText platform 2. **Delivered** - the message has been downloaded by the recipient's device but has not yet been read. 3. **Read** - the message has been read by the recipient For each message sent, the server will provide updates on the delivery status on the event stream which is described in the [Events](doc:events-2) section. For group messages, the message delivery status is captured for each recipient. [block:api-header] { "type": "basic", "title": "Time To Live (TTL)" } [/block] Each message has a Time To Live (TTL). This can range from a few seconds when Delete on Read (DOR) is activated or up to 30 days. Once the message exceeds its TTL, the message will self destruct and be removed from the platform. While each message can have separate TTLs, the lifespan can also be managed at the [Organization](doc:organizations) level. In the case the [Organization](doc:organizations) has the lifespan set, the message lifespan will be adjusted to the lower of the two lifespan settings. Each client is responsible for managing and adhering to lifespan settings indicated by the platform. It is important for security purposes to continue to delete messages once expired. [block:api-header] { "type": "basic", "title": "Message Recall and Delete" } [/block] Messages can be recalled by the message sender. When a message is successfully recalled, the message will no longer exist on both the sender and receiver clients. Keep in mind, a [User](doc:messaging-users-and-groups) is unable to recall messages that they did not send. However, the receiver can delete the message from their client. Note: deleting a message does not remove the message from the Sender's clients. [block:api-header] { "type": "basic", "title": "Attachments" } [/block] Messages can contain various attachments which are similarly secured and encrypted both at rest and in transit. Similarly, attachments are marked with a Time To Live and can be recalled by the sender. Currently the platform supports attachments up to 10MB in size for the several data file types including the following: **Images: ** - JPEG (.jpg) - PNG (.png) - GIF (.gif) **Documents** - Adobe (.pdf) - Word (.doc, .docx) - Excel (.xls, .xlsx) - Powerpoint (.ppt, .pptx) **Audio / Video** - MediaPlayer (.mov, .mp4, m4v) - MP3 (.mp3) - Waveform (.wav) [block:api-header] { "type": "basic", "title": "Message Token" } [/block] Each message has a unique message token. You are able to use the token to get information about a message. See the [/message/:message](doc:messagemessage-id)] documentation for an example.