{"_id":"569fb6a8b4f2d31900898ced","user":"55116f88e2990b0d00fb0552","version":{"_id":"568fce2b04440a1700e4cb4a","project":"568fce2a04440a1700e4cb47","__v":20,"createdAt":"2016-01-08T14:56:43.101Z","releaseDate":"2016-01-08T14:56:43.101Z","categories":["568fce2b04440a1700e4cb4b","568fd1b8b700ce0d002f4b1c","568fd23804440a1700e4cb5b","568fd2444719c119002ce5d8","568ff21204440a1700e4cbc1","5693732c8aa8040d009f2c28","5693738393445b0d00abdad0","5693740093445b0d00abdad1","56937445974aaa0d001ca699","5693b82173f48f0d0075c90d","5694c4cd1005590d0062cb25","569f854466a5640d00efa54c","56a264cdd15dd70d008d825b","56aa56bf318e6c1700a19ddb","56b0e6347ae4550d000627bd","56b200c0f48f270d00e0de6f","56b200c6f48f270d00e0de70","56b22a9665ddf50d0076ba40","56e92ef71996862200fd7f42","574d6577fb835c0e00ca316a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"githubsync":"","__v":5,"parentDoc":null,"project":"568fce2a04440a1700e4cb47","category":{"_id":"568fd1b8b700ce0d002f4b1c","pages":["568fd72c769f210d0013252d","568febf9b700ce0d002f4b61","568fef14769f210d00132570","5694c4f55f1c951900644dda"],"version":"568fce2b04440a1700e4cb4a","__v":4,"project":"568fce2a04440a1700e4cb47","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-08T15:11:52.382Z","from_sync":false,"order":6,"slug":"http-services","title":"HTTP API"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-01-20T16:32:40.008Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"The HTTP Messaging API allows you to send messages and receive receipts and inbound messages using a simple HTTP GET interface and is suited to systems that send low volumes non bulk messages.\n\n##Security\nThe HTTP Messaging API is offered as HTTPS only to ensure data privacy. We use only TLS 2048 bit encryption. We do not support SSL 2.0 or 3.0.\n\nRequests to the API are authenticated with user and password fields contained within the request URL. Your credentials are secure as they are transmitted via HTTPS.\n\n[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"Any non GSM character will cause your SMS to be sent as a Unicode message\",\n  \"body\": \"If your message contains **any** characters that are not included in the [GSM](https://comapi.zendesk.com/hc/en-us/articles/206917189-GSM-Alphabet-Character-Set-) or [Extended GSM](https://comapi.zendesk.com/hc/en-us/articles/206917189-GSM-Alphabet-Character-Set-) character sets then the message will be encoded entirely as Unicode (UTF-16) and therefore each character will take 16 bits instead of 7 bits more than **halving the amount of characters per SMS and potentially doubling your costs!**\\n\\nFind out more about [SMS Message Encoding](doc:message-encoding)\\nFind out more about [SMS Message Segmentation](doc:message-segmentation)\"\n}\n[/block]","excerpt":"","slug":"http-messaging-overview","type":"basic","title":"Overview"}
The HTTP Messaging API allows you to send messages and receive receipts and inbound messages using a simple HTTP GET interface and is suited to systems that send low volumes non bulk messages. ##Security The HTTP Messaging API is offered as HTTPS only to ensure data privacy. We use only TLS 2048 bit encryption. We do not support SSL 2.0 or 3.0. Requests to the API are authenticated with user and password fields contained within the request URL. Your credentials are secure as they are transmitted via HTTPS. [block:callout] { "type": "danger", "title": "Any non GSM character will cause your SMS to be sent as a Unicode message", "body": "If your message contains **any** characters that are not included in the [GSM](https://comapi.zendesk.com/hc/en-us/articles/206917189-GSM-Alphabet-Character-Set-) or [Extended GSM](https://comapi.zendesk.com/hc/en-us/articles/206917189-GSM-Alphabet-Character-Set-) character sets then the message will be encoded entirely as Unicode (UTF-16) and therefore each character will take 16 bits instead of 7 bits more than **halving the amount of characters per SMS and potentially doubling your costs!**\n\nFind out more about [SMS Message Encoding](doc:message-encoding)\nFind out more about [SMS Message Segmentation](doc:message-segmentation)" } [/block]