{"__v":31,"_id":"563d2e24260dde0d00c5eab7","category":{"__v":4,"_id":"55f0b2b5f3735d0d00691fff","pages":["55f0b2b6f3735d0d00692002","563d2b298894d20d00014f44","563d2e24260dde0d00c5eab7","564139c68199950d00648a15"],"project":"55f0757d4624ec2d00814345","version":"55f0b2b5f3735d0d00691ffe","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-09T18:07:58.231Z","from_sync":false,"order":0,"slug":"getting-started","title":"Getting Started"},"parentDoc":null,"project":"55f0757d4624ec2d00814345","user":"55f0756a1e63fc37004b8d2b","version":{"__v":9,"_id":"55f0b2b5f3735d0d00691ffe","project":"55f0757d4624ec2d00814345","createdAt":"2015-09-09T22:29:09.118Z","releaseDate":"2015-09-09T22:29:09.118Z","categories":["55f0b2b5f3735d0d00691fff","55f0b2b5f3735d0d00692000","55f0b2b5f3735d0d00692001","55f0bd67d5d8fc0d00ca6f44","55f0cde9d5d8fc0d00ca6f55","563a8a62a8ba320d00106830","563a8ac9a8ba320d00106832","563d410f31f7580d00511e53","563d411de79f670d00a10a5f","563d412a31f7580d00511e54","566a206f74d574170070b640"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"2.0.0","version":"2"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-11-06T22:48:04.592Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"Now that you have sent and received your first TigerConnect message, you are probably wondering how you can leverage the platform for your particular use case.  Fortunately, there are several ways to integrate TigerConnect. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"REST API\"\n}\n[/block]\nThe TigerConnect API is a RESTful interface, providing programmatic access to much of the data in the system. It provides URLs for accessing TigerConnect objects, and uses built-in HTTP features to receive commands and return responses. This makes it easy to communicate with from a wide variety of environments, from command-line utilities to gadgets to the browser URL bar itself.\n\nTo learn more, check out the [REST API](doc:rest-api) documentation.\n\nIn addition to our API we also have several web and mobile libraries to help simplify and accelerate development. These SDKs were built to manage the following areas so you don't have to.  \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"TigerConnect SDKs\"\n}\n[/block]\nCurrently we have SDKs for the following platforms:\n- [JS SDK](doc:javascript-quick-start) \n- [iOS SDK](doc:ios-quick-start) \n- [Android SDK](doc:android-quick-start) \n- [.NET SDK](doc:dotnet-quick-start)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Benefits of our SDKs\"\n}\n[/block]\n1.  Security - As an enterprise-grade solution, the SDKs ensure that all messages are encrypted both in transit and at rest.  Furthermore, the SDKs take care of managing message lifespans, purging any encrypted messages.  \n\n2.  Networking -  The SDKs manage the connecting to the TigerConnect platform and efficiently receive, process and acknowledge all the events that are delivered by the server.  Don't spend time working through cURL commands and interact with native objects instead.  \n\n3.  Persistence - Keeping things synced across multiple clients is not easy, especially when you are dealing with mobile networks that can be spotty at best.  Our SDKs take care of this for you so that your users have a snappy, responsive user interactions.","excerpt":"","slug":"integrating-tigerconnect","type":"basic","title":"Integrating TigerConnect"}

Integrating TigerConnect


Now that you have sent and received your first TigerConnect message, you are probably wondering how you can leverage the platform for your particular use case. Fortunately, there are several ways to integrate TigerConnect. [block:api-header] { "type": "basic", "title": "REST API" } [/block] The TigerConnect API is a RESTful interface, providing programmatic access to much of the data in the system. It provides URLs for accessing TigerConnect objects, and uses built-in HTTP features to receive commands and return responses. This makes it easy to communicate with from a wide variety of environments, from command-line utilities to gadgets to the browser URL bar itself. To learn more, check out the [REST API](doc:rest-api) documentation. In addition to our API we also have several web and mobile libraries to help simplify and accelerate development. These SDKs were built to manage the following areas so you don't have to. [block:api-header] { "type": "basic", "title": "TigerConnect SDKs" } [/block] Currently we have SDKs for the following platforms: - [JS SDK](doc:javascript-quick-start) - [iOS SDK](doc:ios-quick-start) - [Android SDK](doc:android-quick-start) - [.NET SDK](doc:dotnet-quick-start) [block:api-header] { "type": "basic", "title": "Benefits of our SDKs" } [/block] 1. Security - As an enterprise-grade solution, the SDKs ensure that all messages are encrypted both in transit and at rest. Furthermore, the SDKs take care of managing message lifespans, purging any encrypted messages. 2. Networking - The SDKs manage the connecting to the TigerConnect platform and efficiently receive, process and acknowledge all the events that are delivered by the server. Don't spend time working through cURL commands and interact with native objects instead. 3. Persistence - Keeping things synced across multiple clients is not easy, especially when you are dealing with mobile networks that can be spotty at best. Our SDKs take care of this for you so that your users have a snappy, responsive user interactions.