In Development • 2026 API Roadmap

Advanced API & Integrations.
Built Directly Into Your
CRM & TMS.

Eliminate fragmented telecom workflows. Embed Dialxa's sub-50ms WebRTC voice engine directly into your logistics dispatching platforms, transport management systems, or sales pipelines.

Features in Active Engineering (Private Beta Sandbox)

Advanced API endpoints, TMS/CRM connectors, and programmatic provisioning pipelines are currently under active development in our engineering lab. Below are three architectural commitments we are releasing first to Early Access design partners.

Status: Engineering & Pilot Testing API Version: v1-preview Sandbox: By Invitation
Three Integration Pillars

What Will You Build with Dialxa Developer API?

Engineered for mission-critical operations where teams cannot afford manual dialing errors or fragmented call data.

PILLAR 01 In Development

Native "Click-to-Call" Directly Embedded in Your CRM or TMS

Dispatchers and sales representatives never re-type a number or pick up a desk handset. A single click on an active order immediately bridges the call to driver or client.

With our lightweight WebRTC integration and REST APIs, embed a native calling button into any modern web-based Transport Management System (TMS such as FireTMS, Trans.eu, Transporeon, SAP TM) or CRM (Salesforce, HubSpot, Pipedrive, custom portals). Voice connects with sub-50ms latency directly inside the browser.

  • Zero manual dialing: Eradicate misdials to drivers, carriers, and international customers.
  • Real-time order context: Pass freight IDs, route origins, and vehicle data directly into the active in-call header.
  • Pure browser engine: No external softphone installations, desktop bloatware, or hardware phones.
TMS Dispatch Panel • Order Inspector
#TMS-8921-EU

Route: Warsaw (PL) → Rotterdam (NL)

In Transit • On Schedule
Peter Williams (Driver)

+48 601 234 567 • Truck ID: WZ 99281

↑ Click the "Call Driver" button to test the live TMS dispatch calling simulation.

Webhook Event Payload: call.completed HTTP 200 OK • 24ms
{
  "event": "call.completed",
  "call_id": "dlx_9428f81a",
  "caller": {
    "agent_id": "usr_dispatch_04",
    "name": "Mark Hansen",
    "extension": "204"
  },
  "destination": "+48601234567",
  "timing": {
    "started_at": "2026-09-15T14:10:02Z",
    "duration_seconds": 184,
    "billable_seconds": 184
  },
  "metrics": {
    "mos_score": 4.48,
    "average_latency_ms": 22
  },
  "recording_url": "https://vault.dialxa.com/rec/9428f81a.wav"
}
PILLAR 02 In Development

Automated Call Detail Records (CDR) Streamed Directly to Your Analytics

Who spoke to whom, when, and for how long — full telemetry streams instantly into your data warehouse, PostgreSQL, or PowerBI dashboards.

Eliminate manual CSV downloads at month-end or uncertainty over whether an operator reached the carrier. After every call, Dialxa dispatches an immediate Webhook event to your endpoint, enriching customer activity history in your CRM and keeping reporting tables current in real time.

  • Complete CDR telemetry: Precise call duration, timestamps, termination reason, and agent identifiers.
  • Native webhooks & REST API: Streamlined ingestion into BigQuery, PostgreSQL, Snowflake, or custom data pipelines.
  • Auditing and settlement: Encrypted audio recordings programmatically linked to transport orders and customer tickets.
PILLAR 03 In Development

Zero-Touch Programmatic User Provisioning

When a new employee joins your team, your HR or Identity system automatically provisions their Dialxa voice account via API.

Save IT and operations teams hours of repetitive administration. No more logging into legacy telecom portals each time you hire a dispatcher or account manager. Your identity provider (Okta, Active Directory, HRMS, or custom internal portal) sends a single API request, and the employee's Dialxa extension, outbound permissions, and routing profile are live in seconds.

  • Onboarding in under 1 second: Instant extension assignment, national/international dialing rules, and outbound caller ID.
  • Immediate offboarding: When an employee departs, HR deactivation revokes lines and recycles license seats automatically.
  • SCIM 2.0 & REST standard compliance: Purpose-built for modern cloud directory synchronization.
1. New Employee Added in HRMS / Directory

HR creates account: john.doe@company.com as Senior Freight Dispatcher.

2. API Webhook Trigger: POST /v1/users/provision

Customer system calls Dialxa endpoint with role configuration and number pool.

3. Account Active in Under 500ms

Extension #214 assigned. Dispatcher can make calls directly from the browser with zero IT overhead.

Architecture Comparison

Legacy Telecom vs. Dialxa Developer API

See how direct workflow integration eliminates human friction, reduces errors, and automates records.

Przesuń w prawo, aby zobaczyć Dialxa API →
Capability Legacy PBX & Desk Telephony Dialxa Developer API
Call Initiation Manual retyping of phone numbers from TMS/CRM screens onto desk phones or mobile devices. Single click on the "Call" button directly inside the TMS/CRM order card. Connects in <50ms.
Call Logs & Analytics (CDR) Manual CSV exports once a month from PBX admin consoles; zero correlation to active orders or deals. Real-time Webhook and REST API streaming call telemetry to your reports and databases instantly.
Employee Onboarding & Provisioning IT ticketing, manual PBX account creation, SIP credential generation, and physical handset configuration. 100% programmatic provisioning via REST/SCIM API — extension and route policies active instantly.
Client Infrastructure Bloated desktop softphones, proprietary desk phones, local PBX or Asterisk maintenance. Pure browser-native WebRTC protocol, zero downloads, zero hardware overhead.
Private Beta Enrollment

Join the Early Access Design Program

Building a modern TMS, managing a transport fleet, or scaling a high-velocity sales team? Apply for our private developer sandbox and help shape the future of our API.

Thank you for your application!
We have registered your request for early access to the Dialxa Developer API. An integration engineer will contact you shortly to configure your Sandbox environment.

Privacy Policy

§ 1. General Provisions

This Privacy Policy sets out the rules for the processing and protection of personal data provided by Users in connection with their use of the dialxa.com website and the Dialxa SaaS platform.

The Administrator of personal data contained in the website is:
DIALXA SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
Registered Office: Juliusza Słowackiego 37J, 80-257 Gdańsk, Poland
KRS: 0001270642
Tax ID (NIP): 5842890706
hereinafter referred to as the "Administrator".

Contact with the Administrator is possible via e-mail: support@dialxa.com.

For the sake of security of the data entrusted to us, we have developed internal procedures and recommendations to prevent data access by unauthorized persons.

Personal Data is processed on the basis of the consent expressed by the User and in cases where legal provisions authorize the Administrator to process personal data on the basis of legal provisions or for the purpose of implementing a contract concluded between the parties.

§ 2. Scope and purpose of data collection

The website performs functions of obtaining information about users and their behavior in the following ways:

  • Through voluntarily entered information in forms (name, surname, e-mail, phone number, company name).
  • Through the collection of "cookies".

The data provided in the form is processed for purposes resulting from the function of a specific form, e.g., to process a contact request, create an account on the platform, or present a commercial offer.

§ 3. External Tools

The website uses external tools to handle contact forms.

The User acknowledges that the data entered in the contact form is sent via the service provider's servers in order to deliver the e-mail message to the Administrator.

The provider may process some technical data (e.g., IP address) for security and spam prevention purposes. More information can be found in the privacy policy of the respective provider.

§ 4. User Rights (GDPR)

The User has the following rights under the GDPR:

  • The right to access their personal data,
  • The right to rectify data,
  • The right to delete data ("the right to be forgotten"),
  • The right to restrict processing,
  • The right to data portability,
  • The right to object.

In order to exercise the rights referred to above, you can send an appropriate e-mail to: support@dialxa.com.

§ 5. Cookies

The website uses cookies. These are small text files sent by a web server and stored by the browser's computer software.

Cookies are used for statistical and functional purposes (e.g., remembering a session). The User can disable cookies in their browser at any time.

Terms of Service

§ 1. General Provisions

These Terms of Service specify the rules for using the website available at dialxa.com.

The Service Provider and Administrator of the Website is:
DIALXA SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
Registered Office: Juliusza Słowackiego 37J, 80-257 Gdańsk, Poland
KRS: 0001270642
Tax ID (NIP): 5842890706
hereinafter referred to as the "Service Provider".

Contact with the Service Provider is possible via e-mail: support@dialxa.com.

These Terms of Service are the regulations referred to in Art. 8 of the Act of July 18, 2002, on the provision of electronic services.

§ 2. Types and scope of services

The Service Provider provides electronic services via the Website consisting of:

  • Providing users with informational content regarding the offer of the Dialxa SaaS VoIP platform.
  • Providing a contact form enabling the sending of inquiries.

Using the above services is voluntary and free of charge.

The agreement for the provision of an electronic service consisting of browsing the Website's content is concluded for a definite period and terminates when the User closes the Website.

The agreement for the provision of a service consisting of making a contact form available is concluded for a definite period and terminates when the message is sent or when the User stops sending it.

§ 3. Conditions and technical requirements

In order to properly use the Website, the User should have:

  • A device with Internet access,
  • A modern web browser (e.g., Google Chrome, Mozilla Firefox, Microsoft Edge, Safari) that supports cookies,
  • An active e-mail account (if they wish to use the contact form).

It is forbidden for the User to provide illegal, offensive, misleading content or content that may disrupt the operation of the Service Provider's ICT systems (e.g., spam, malicious software).

§ 4. Nature of commercial information

Information provided on the Website, including price lists and service descriptions, does not constitute an offer within the meaning of Art. 66 of the Civil Code, but rather an invitation to conclude a contract (Art. 71 of the Civil Code).

Detailed conditions of cooperation, scope of work, and pricing are agreed upon individually with the Client via a separate contract or confirmed order.

The Service Provider reserves the right to change the content on the website at any time, without prior notice to Users.

§ 5. Complaint procedure

The User has the right to submit complaints regarding the operation of the Website (e.g., technical errors, malfunctioning form).

Complaints should be submitted electronically to: support@dialxa.com.

The complaint should include: a description of the problem, the date of its occurrence, and the User's contact details.

The Service Provider will process the complaint within 14 days of its receipt.

§ 6. Personal data protection

The Administrator of personal data processed within the Website is the Service Provider mentioned in § 1.

Detailed rules for processing personal data and using cookies are described in the Privacy Policy, available under a separate link on the Website.

§ 7. Final Provisions

In matters not covered by these Terms of Service, the provisions of Polish law apply, in particular the Civil Code and the Act on the provision of electronic services.

The Service Provider reserves the right to change the Terms of Service. Changes come into force upon their publication on the Website.