The Burner API enables programmatic access to core telephony functions like sending and receiving messages and media, as well as the "business logic" layer the company spent years building.
Key Burner features include per-line configuration and settings, contact management, blocking and muting, content filtering, text auto-responses, and more.
Full API access to Burner means developers can now build integrations that enhance and extend Burner's messaging and application capabilities in ways the company believes represent the future of smart phone numbers.
Developers can also take advantage of this API to embed Burner's basic and enhanced calling and messaging experiences into their apps via OAuth. Your users get all the benefits and features of our top-rated voice and messaging client (and the support and business functions that stand behind it), while you get all the benefits of controlling the phone number at the network level. In effect, you can treat the Burner app itself as a service, rather than building your own "last mile" on top of a bare-bones telephony API.
The following is a list of SDKs from our SDK directory that matched your search term. Though your definition of an SDK may differ, in our world, we define SDKs as platform- specific tools for consuming existing APIs of the sort we list in our API directory. For example, the Ruby SDK for consuming the Twitter Ads API. If you think an SDK, API, or other asset is missing from our directory, be sure to check our guidelines for making contributions to ProgrammableWeb.
The Burner React JS SDK by Burner interacts with the API to build applications with disposable numbers. It includes a walkthrough with authentication, display list of burners, and response to messages.