Skip to contentSkip to navigationSkip to topbar
On this page

Listings Overview


Listings are pre-integrated partner technologies available in the Marketplace catalog. Listings make it possible to quickly build rich communications experiences using the Twilio API and third-party capabilities. You can choose the right technology for your needs without having to learn, test, and manage different platforms.

View all the Twilio Marketplace Listings in the Marketplace catalog(link takes you to an external page).


Listing categories

listing-categories page anchor

Marketplace supports four categories of Listings:

  • No-code Partners: No code required for integration.
    • Twilio.org: A subcategory of No-code Partners for non-profit organizations.
  • Add-ons: Code required for integration.
  • Pay Connectors: Add-ons for payment processors.
  • Stream Connectors: Add-ons for Media Streams.

No-code Partners

no-code-partners page anchor

No-code Partner Listings offer out-of-the-box solutions supported by Twilio partners, requiring no technical expertise to install, configure, and use.

You can use No-code Partner Listings to integrate Twilio features into your workflows more quickly. Follow the installation and configuration instructions on the Listing's details page. After installing a No-code Partner Listing to your Twilio Account, you'll complete the remainder of the Listing's onboarding and enablement process on the partner's platform.

Twilio.org

twilioorg page anchor

Twilio.org Listings are a subcategory of No-code Partner Listings that specifically support non-profit organizations.

Add-on Listings integrate third-party services with Twilio's APIs and require code for implementation.

Add-ons enhance Twilio's capabilities by embedding external data directly into Twilio API responses. For example, an Add-on Listing for the Twilio Lookup API might use an additional data source for information about a phone number, and then include that information in the response to your API request.

An Add-on Listing can have zero or more Extensions enabled. An Extension describes the specific feature or API endpoint of a Twilio product in which an Add-on Listing can be used. For example, an Add-on for Twilio Programmable Voice might have Extensions for Outgoing and Incoming Voice Calls. You can select the Extensions you want to include when configuring the Add-on.

The following table lists the supported Extensions. Each Add-on listing supports one or more Extensions.

ProductExtension Friendly NameExtension Unique Name
LookupLookupslookup-api
Programmable SMSIncoming SMS Messagesms-incoming
TaskRouterCreate TaskRouter Taskstaskrouter-create-task
Programmable VoiceIncoming Voice Callvoice-incoming
Programmable VoiceRecord Verb Recordingsrecording-verb
Programmable VoiceOutgoing Call (API) Recordingsrecording-api
Programmable VoiceConference Recordingsrecording-conference
Programmable VoiceDial Verb Recordingsrecording-dial

Pay Connectors are Add-ons that integrate with payment processors and require code for integration. Learn more about Pay Connectors.

Stream Connectors are Add-ons that integrate with Media Stream recording, transcription, and analysis. Stream Connectors require code for integration. Learn more about Media Streams.


Partners set their own pricing for Marketplace Listings.

No-code Partners handle billing on their platform; Twilio isn't involved in the billing for your usage of these Listings. Most No-code Partner Listings are billed directly through the partner.

Add-ons invoke the Twilio Billing system for usage-based billing. Twilio meters the Listing usage and deducts the cost from your account balance.

You can check pricing for Listings in the Marketplace catalog(link takes you to an external page). View your Add-on usage in the Usage page in the Console(link takes you to an external page).


Refer to the Listing's detail page in the Marketplace catalog(link takes you to an external page) for support information, including partner phone numbers, email, expected resolution times, and support process.

When you contact Twilio or a partner to request support for a Listing, provide the following information to help identify and resolve your issue.

IdentifierWhat is itWhere to find it
Installed Add-on SIDA unique identifier for a single instance of an installed Listing of an Account, beginning with XE. Example: XEaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaAvailable in the Console, under the Configure tab of the Listing's detail page in the Marketplace catalog(link takes you to an external page).
Add-on SIDA unique identifier of a Listing, beginning with XB. Example: XBaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaAvailable in the Console, on the Installed Modules page(link takes you to an external page) and the Listing's detail page in the Marketplace catalog(link takes you to an external page).

The following table outlines when to contact Twilio for Add-on Listing-related issues and when you need to reach out to the Add-on Listing's partner.

IssueSupport provided by
Add-ons parameter isn't in your callbacksTwilio
Error Codes 61000, 61003, 61006, 61009Twilio
Error Codes 61001, 61002, 61004, 61005, 61007, 61008Listing Partner
Error Codes not listed in this tableTwilio
Results aren't accurate or as per expectations specified in the Add-on Listing's documentationListing Partner

When you contact Twilio or a partner to request support for an Add-on, provide the following information to help identify and resolve your issue.

IdentifierWhat is itWhere to find it
Add-on Unique NameHuman-readable unique identifier for an instance of an installed Listing. Examples: twilio_caller_identity, twilio_caller_identity_2.Available in the Console, under the Configure tab of the Listing's detail page in the Marketplace catalog(link takes you to an external page).
Request SIDThe unique identifier of a particular Add-on request. Used for billing and debugging. Example: XR000009775bb6d43d1cabc4955723fae1This is available in the API response or callback you receive from Twilio that contains the Add-on results.
Installed Add-on SIDA unique identifier for a single instance of an installed Listing of an Account, beginning with XE. Example: XEaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaAvailable in the Console, under the Configure tab of the Listing's detail page in the Marketplace catalog(link takes you to an external page).
Add-on SIDA unique identifier of a Listing, beginning with XB. Example: XBaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaAvailable in the Console, on the Installed Modules page(link takes you to an external page) and the Listing's detail page in the Marketplace catalog(link takes you to an external page).