Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Plivo 10DLC (BYOK) — connector documentation

  • MCP endpoint: https://byok-plivo-10dlc.connectorbay.com/mcp
  • REST API: POST https://byok-plivo-10dlc.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-plivo-10dlc.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Plivo 10DLC Auth ID, sent in the X-Upstream-Key header and the Auth Token in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-plivo-10dlc.connectorbay.com/health · Tool schemas: https://byok-plivo-10dlc.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-plivo-10dlc · agent@connectorbay.com

What Plivo 10DLC (BYOK) is for

Plivo 10DLC (BYOK) lets an AI assistant read your own Plivo 10DLC data through the Plivo 10DLC API with a key you supply (Auth ID). Read-only: 9 tools (list_brands, get_brand, get_brand_usecases, list_campaigns, get_campaign, list_campaign_numbers, get_campaign_number_status, list_tollfree_verifications, get_tollfree_verification). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.plivo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Plivo 10DLC. Plivo 10DLC and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which of my Plivo 10DLC brands are registered?"
  • "What is the vetting status of Plivo brand BVMN1EM?"
  • "Which campaign use cases can my Plivo brand register?"
  • "Which Plivo 10DLC campaigns failed registration?"
  • "What are the carrier throughput limits of Plivo campaign CY5JZZZ?"
  • "Which of my Plivo numbers are linked to campaign CY5JZZZ?"

What it does

  • list_brands: List 10DLC brands with type, entity type, vertical, website, registration status, vetting status and score. Tax IDs, addresses and contact details are not returned.
  • get_brand: Get one 10DLC brand: type, entity type, vertical, website, registration status, vetting status and score, declined reasons. Tax IDs, addresses and contact details are not returned.
  • get_brand_usecases: List the campaign use cases a brand is allowed to register, with code, name and details.
  • list_campaigns: List 10DLC campaigns with brand, use case, registration status, error reason, source, attributes and carrier throughput metadata. Sample message texts are not returned.
  • get_campaign: Get one 10DLC campaign: brand, use case, registration status, error details, attributes (embedded links, opt-in, opt-out, help) and carrier throughput metadata.
  • list_campaign_numbers: List the phone numbers linked to a 10DLC campaign with the linking status of each.
  • get_campaign_number_status: Get the campaign linking status of one of your numbers (digits only, with country code).
  • list_tollfree_verifications: List toll-free number verification requests with use case, summary, volume, opt-in type, status and error message. Sample messages are not returned.
  • get_tollfree_verification: Get one toll-free verification request by UUID: number, use case, summary, volume, opt-in type, status and error message.

BYOK key

You bring your own Plivo 10DLC Auth ID (https://cx.plivo.com/home). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.plivo.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Plivo 10DLC API (api.plivo.com) with a BYOK key; documentation: https://www.plivo.com/docs/messaging/api/10dlc/overview. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Plivo 10DLC. Plivo 10DLC and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Plivo 10DLC account.

Built for: Worldwide. Languages: English.