Menu

Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Marketplace Offerings

The first type of product available in the Marketplace is an Add-on.

Add-ons are pre-integrated partner technologies that let developers do more with the Twilio API. They make it possible to quickly build rich communications experiences by combining Twilio and 3rd-party capabilities by giving you the ability to choose the right technology for your needs without having to learn, test, and manage different platforms.

Add-ons are available through the Twilio Marketplace; developers can choose from a list of verified Add-ons and install them in a single click. Once installed, they enhance Twilio APIs to deliver the partner capability, such as returning the spam score of a phone number or providing sentiment analysis for a message.

At a functional level, Add-ons package Partner APIs, and annotate the content that Twilio provides by tapping into the Partner’s data sources or using Partner’s technology to analyze the content. Examples include Phone number based queries for demographic & marketing data, Number fraud/spam blacklist, Recordings Transcription, Message sentiment analysis, etc.

Currently, the following Twilio content is available for Add-on partners to build with : Phone Numbers, Incoming Message body, Call recordings.

Add-on Type Available Integration Point(s) for Customers Data available to Partners Consumption Mode
Phone Number Add-on Lookups, Incoming SMS, Incoming Voice Phone Number (single, to, from) Synchronous
Message Analysis Add-on Incoming SMS Phone Numbers, Message Body Synchronous
Recording Analysis Add-on Recordings Audio File (single channel) Asynchronous

Developers select an Add-on and configure it for their account, making it available for use. They can then specify that they want it invoked when using a supporting Twilio API.

Add-on Flow

image alt text

Pricing & Billing

The Marketplace allows Partners to set their own pricing for their Add-ons and invokes the Twilio Billing system for usage-based billing. Use of a partner’s Add-on will be metered by Twilio and deducted from the developers account. The amount billed will be distributed to partners at regular intervals, less a transaction fee, via an invoice.

The following billing models are supported by the Marketplace for an Add-on:

  • Pay-per-use

  • Pay-per-success (TBD) : Conditional billing subject to absence of certain JSON elements in the response and HTTP status codes.

  • Pay-per-minute : For Transcription / Recording Add-ons

Packaging Partner Service into Add-ons

Partners can offer one or more Add-ons in the marketplace. They can choose to package 1 service/API into one Add-on, or deliver 1 service/API as multiple Add-ons, each with a specific use case and associated pricing. Examples of the latter include different kinds of data sets (Business vs Consumer information) or Transcription for different languages.

Partner Accounts

Currently, Twilio supports one ‘master’ account per Partner offering, and will use that to make all API requests.

Example

Let’s say you have an web service that takes a phone number and returns all the english mnemonics you can spell with it. You’d like to let any Twilio customer dip your service via the Twilio Lookup API to see potential results, and you want to charge $0.0001 per lookup.

Assume that this is delivered by the following API (ignoring credentials for the time being):

https://www.example.com/twilio_phone_number_example  -d "e164=+18778894546"

Results in the following JSON response :

{
"anagrams": ["+18778TWILIO", ...]
}

You would deliver this service as a marketplace Add-on -- ‘Anagram’, which contains all the marking and documentation collateral, as well as configuration pointing at the URL for a web service that confirms to Twilio's specification for phone number lookup services. A Twilio developer finds and installs this service on their account. They now would have the ability to use the Anagram Add-on in the Lookup API, when buying/provisioning phone numbers, receiving incoming calls or messages, or making outgoing calls or messages, if appropriate.

curl -X GET https://lookups.twilio.com/v1/PhoneNumbers/18778894546\
-d "AddOns=partner_anagrams" -u "{TwilioAccountSid}:{TwilioAuthToken}"

Would result in a 200 OK response with the body:

{
    "country_code": "US",
    "phone_number": "+18778894546",
    "national_format": "1 (877) 889-4546",
    "url": "https://lookups.twilio.com/v1/PhoneNumber/+551155256325",    
    "add_ons": {  
           "status": "successful",
           "message": null,
           "code": null,
           "results": {      
                    "partner_anagrams": {
                           "request_sid": "XRc1479687aadf64c62e6ab2b6e0077a1a",
                           "status": "successful",
                           "message": null,
                           "code": null,
                           "result": {
                                   "anagrams": ["+18778TWILIO"]
                           }                           
                    }
            }
    }
}

When invoked, Twilio will call out to your HTTP service and post the requested phone number. Upon receiving the results, it will take the JSON body of those results and included them in the response payload along with the other types requested.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.