Dex Platform

Intermedia

Administer your Intermedia partner account from Dex - customer accounts, users, licenses, phone numbers, trunks, and billing.

Dex connects to the Intermedia Partner API v3 so MSPs can run their cloud communications business conversationally - manage customer accounts, provision users and seats, buy and cancel licenses, import and release phone numbers, and read billing plans and usage. Available out of the box as an MSP global app: the partner holds one API client credential, and each Dex child tenant is confined to its own Intermedia account GUID (the identifierKey account_id), so a customer only ever sees its own users, numbers, and spend. This covers the Partner API only - the Intermedia Extend API for calling, voicemail, chat, and meetings needs a separate per-account credential and cannot be reached from a partner credential.

Start with $100 free →See Dex Live

What Dex does with Intermedia

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Browse the partner customer roster and read account, company, and external-field details
Provision, update, and remove users (mailboxes/seats) on a customer account
Manage portal-login contacts and their access roles
Buy and cancel licenses, and check whether a product is purchasable before proposing a purchase
Import and release phone numbers across trunks and locations, and read numbers history
Read and change billing plans, write payment details, and read the partner usage report
Manage account limits, quotas, and account state (enable/disable)
Deploy out of the box as an MSP global app - one partner credential, each customer confined to its Intermedia account GUID

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>List the customer accounts under our partner and break them down by plan
>Add a user named Dana Rivera (dana.rivera@contoso.com) to the Contoso account
>How many licenses does Northwind have, and which are unassigned?
>Import these DIDs onto the London trunk for Acme and let me know when they go live
>Disable the Fabrikam account - tell me what will break first

How to configure Intermedia

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the Intermedia Partner Portal, go to Integrations > Public API > Create a New API Client and check Enable Client.
2
Copy the Client ID and Client Secret - the secret is shown once, at creation. If it was not saved, create a new API client.
3
In Dex, enable the Intermedia integration and paste the Client ID and Client Secret. Leave account_id blank on the MSP master connection.
4
Dex validates the credential with a live call before saving.
5
For MSPs, deploy as a global app - Dex maps each child tenant to its Intermedia account GUID (the customerID from GET /api/accounts) and confines every call to that account.

Credentials required

client_id: Partner API Client ID from the Intermedia Partner Portal (Integrations > Public API), with Enable Client checked
client_secret: Partner API Client Secret - shown once at creation; create a new API client if it was lost
account_id: Per-tenant Intermedia account GUID (32 hex digits, with or without dashes). Blank on the MSP master connection; set on each child tenant for per-account isolation

Requirements

•An Intermedia partner account with Partner API access and an enabled API client
•Some partner accounts require Intermedia Support to attach a partner contact to the API client before it works
•The Partner Account Usage Report must be switched on by Intermedia Support before usage data returns
•Covers the Partner API only - calling, voicemail, chat, and meetings need a separate per-account Intermedia Extend integration
•For MSPs, deploys as a global app with per-tenant account-GUID scoping