Developer Documentation

Programmable Canadian Telecom

Provision SIP trunks, search and assign DIDs and toll-free numbers, manage E911 and LNP, send SMS and MMS, and query CDRs — all through a single, versioned REST API from a Class 1 Facilities-Based Canadian Carrier.

Request API AccessBrowse Endpoints

50+ endpoints · JSON over HTTPS · Bearer token auth · 100% Canadian data sovereignty

  • DIDs & Toll-Free

    Search, assign, list, and reroute Canadian and North American numbers on demand.

  • SIP Trunks

    Create, update, and destroy SIP trunk routes and destinations programmatically.

  • SMS & MMS

    Enable messaging on any DID or TFN, manage brands and campaigns, send and query messages.

  • E911

    Register, update, and search emergency locations for every number you provision.

  • Number Porting (LNP)

    Submit port requests, update supporting documents, and track port status in real time.

  • CDRs & Billing

    Query voice, SMS, and vFAX call detail records. Pull invoices, payments, and credit notes.

What is the IXICA API?

The IXICA API V2 is a REST API for building and operating telecom services in Canada. Whether you're a service provider automating provisioning, a SaaS platform embedding voice or SMS, or an enterprise integrating an existing PBX, the API gives you programmable control over every part of the IXICA network.

IXICA is a Class 1 Facilities-Based Canadian Carrier. Every DID, every SIP session, every SMS, and every byte of CDR data stays within Canadian jurisdiction and Canadian-owned infrastructure. This matters for financial services, healthcare, government, and any Canadian business governed by data-residency requirements such as PIPEDA, provincial privacy laws, and sectoral compliance frameworks.

Getting Started

To use the IXICA API you need:

  • An IXICA account in good standing — request API access.
  • A Bearer API key issued by your account manager, scoped to your account number.
  • Any HTTPS client capable of POSTing JSON — cURL, Postman, Python requests, PHP cURL, Node fetch, or the language of your choice.

All requests are HTTPS POST with a JSON body and an Authorization: Bearer <key> header. The full endpoint list, parameters, request samples, and JSON response schemas are in the API Endpoint Reference.

Ready to build?

Talk to our team about API access, pricing, and the fastest path to onboarding — or jump straight into the endpoint reference.

Get API AccessAPI Endpoint Reference