Get Started with EnableX
EnableX offers a free trial so you can evaluate Video and Voice capabilities before committing to a paid plan. This guide walks you through signing up, setting up your first project, and getting the credentials you need to call the APIs.
Registration is free and requires only a valid email address and phone number for verification.
Your trial account comes with free credits that you can use to explore the platform. No credit card is required to sign up.
Video and Voice services can be tried immediately after account creation — no additional provisioning is required. You can make API calls, run a video session, and make outbound voice calls within minutes of signing up.
Messaging services (SMS, WhatsApp, RCS) depend on channel-specific provisioning — for example, obtaining a Sender ID or a WhatsApp Business Account. These require a brief setup process and may not be available to test instantly. Contact the EnableX team to expedite provisioning for your trial.
Once registered, log in to the EnableX Portal — your central control panel for everything on the platform:
- Creating and managing projects
- Viewing and rotating API credentials
- Provisioning channel resources (phone numbers, Sender IDs, WhatsApp accounts)
- Monitoring usage, session recordings, and call detail reports
- Managing billing and topping up your wallet
All API access in EnableX is scoped to a project. A project represents one of your applications or services, and it determines which channels are enabled and what credentials are issued.
To create your first project:
- In the portal, navigate to Projects from the left sidebar.
- Click Create New Project.
- Give the project a name (e.g., My Video App, Voice IVR).
- Select the channel or channels you intend to use — Video, Voice, Messaging, or a combination.
- Click Create.
You can create multiple projects — one for each product or environment (development, staging, production).
After creating a project, the portal issues two credentials:
- App ID — A unique identifier for your project. Used as the username in API authentication.
- App Key — A secret key paired with your App ID. Used as the password in API authentication. Treat this like a password — never expose it in client-side code, browser applications, or public repositories.
To view your credentials, open the project in the portal and look in the Credentials or API Keys section.
Your App ID and App Key must only ever be used in your backend (App Server). They must never be embedded in a browser page, a mobile app, or any client-facing code. If a key is compromised, you can rotate it from the portal — old calls using the previous key will immediately stop working.
All EnableX APIs use HTTP Basic Authentication — your App ID as the username and App Key as the password. Most API clients and HTTP libraries handle Basic Auth natively.
Depending on the channels your project uses, the portal provides utilities to configure and procure the resources your service needs:
- Video — No provisioning needed beyond creating the project. You can immediately use the Video API to create rooms and issue tokens. Configure recording storage, CDN delivery, and RTMP destinations from the portal.
- Voice — Configure inbound DID numbers, SIP trunks, and IVR settings. Phone numbers for inbound call routing can be provisioned directly from the portal.
- Messaging — Register Sender IDs for SMS, connect a WhatsApp Business Account, and enable RCS from the portal. Each channel may involve a short approval process depending on your region.
Your trial credits let you evaluate the platform, but have usage limits. To remove those limits and enable production-grade usage, top up your wallet from the portal's Billing section.
EnableX uses a prepaid wallet model — you add funds and usage is deducted as you go. There are no monthly minimums or commitment periods for most channel types.
Trial credits are enough to run a complete integration test for Video and Voice. You do not need to top up before writing and testing your first integration — use the trial period to validate your implementation, then top up when you are ready to go to production.
With your credentials in hand, pick the channel you want to start with:
- Video — Read the Guide — Building a Video Application for an end-to-end walkthrough, then refer to the Video API Reference and your platform's SDK Reference.
- Voice — Start with the Voice Overview, then explore the Voice API Reference. For media streaming and AI integration, see Media Streaming API.
- Messaging — Start with the Unified Messaging API to send SMS, WhatsApp, and RCS from a single endpoint.
Frequently Asked Questions
How do I get started with EnableX?
Create an account on the EnableX Portal, create a project, select the services you need (Video, Voice, or Messaging), and copy your App ID and App Key. Most integrations take under an hour using the provided SDKs. The Portal also includes a step-by-step setup guide for each product.
Is EnableX free to try?
Yes. New accounts receive trial credits upon signup. You can explore the full Video, Voice, and Messaging APIs during the trial period. Billing begins only when trial credits are exhausted or for production-level usage tiers.
What credentials do I need to call the EnableX API?
Each project in the Portal generates an App ID and App Key. These are used as HTTP Basic Auth credentials (App ID as username, App Key as password) on all REST API calls. For Video sessions, you additionally generate short-lived room tokens from your server and pass them to the client SDK.
Do I need to expose my App Key in the app or browser?
No. Your App Key is a server-side secret and must never appear in client-side code, mobile apps, or browser JavaScript. Always call the EnableX API from your server and pass only tokens to clients, not your raw credentials.
Which programming languages and platforms does EnableX support?
EnableX provides SDKs for iOS (Swift/Objective-C), Android (Java/Kotlin), Web (JavaScript), Flutter (Dart), React Native, and Cordova. Server-side API calls can be made from any language that supports HTTP including Node.js, Python, PHP, Java, and Go.