API Reference SMS Conversations Authentication Portability Check Support Inbox Account self-service Voice (beta) Help Log-In Sign Up Introduction Compatibility Adhered web standards Base URLs Sign up for your API key Introduction First off, big thanks for building with tyntec’s APIs! This is where you can access our API reference docs and support for tyntec’s services. This reference will help you build your applications with tyntec’s API endpoints and get the resources you need to use our services. We provide language bindings in Shell, HTTP, JavaScript, Node.JS, Ruby, Python, Java, and Go! You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs on the top right. Explore our public APIs! SMS Learn how to send and receive text messages via our SMS API. Documentation API Reference Conversations Learn how to send and receive messages via our Conversations API. Documentation API Reference Authentication Learn how to use two-factor authentication via SMS programmatically. Documentation API Reference Portability Check Validate phone numbers before sending messages or calling them. Documentation API Reference Support Inbox Check out how to get started with our omni-channel Support Inbox. Documentation API Reference Compatibility We work continuously on our APIs and products behind them to cover new use cases, add new functionalities and improvements suggested by you. During this process, we strive to make these changes as least impactful towards your system as possible. Speaking about the REST APIs, we aim for changes that will not break your implementation. This covers: only adding new properties, sticking with the data types defined, not renaming existing ones. In order to make the communication between your system and ours as frictionless as possible, we recommend to: follow strictly the data definitions when you send requests to our APIs, accept unknown properties when you receive data from our APIs. This recommendation follows the Robustness Principle. Adhered web standards One goal of all our APIs is to follow best practices and standards of HTTP-based services. This is achieved through compliance with the following RFCs: RFC 7231 – HTTP/1.1: Semantics and Content RFC 8259 – JSON RFC 7807 – Problem Details for HTTP APIs Base URLs https://api.tyntec.com Terms and Conditions Support and Service Level Agreements Acceptable Use Policy Data Privacy Statement Disclaimer GDPR Compliance Imprint © 2021 tyntec. All rights reserved