# Alianza > Alianza is a cloud communications software company founded in 2009 and headquartered in Utah, serving more than 1,000 communications service providers across 81 countries. Its Intelligent Communications Fabric — an experience layer, an orchestration layer and an infrastructure layer — is packaged as Alianza One (multi-tenant cloud voice), Alianza Core (physical, virtual and containerized network functions) and Alianza Fusion (hosted core communications systems). The Alianza Public API is a JSON REST API over Alianza One that service providers use to orchestrate partitions, accounts, users, devices, telephone numbers, porting, SIP trunks, calling plans, voicemail, CDRs and reporting. Generated by the API Evangelist enrichment pipeline on 2026-08-02. Alianza publishes no llms.txt of its own (GET /llms.txt returns 404 on api.alianza.com, developer.alianza.com and www.alianza.com), so this file is generated from the provider's published OpenAPI description and developer portal. ## API - [Alianza Public API](https://developer.alianza.com/provisioning-api): JSON REST API for the Alianza One cloud communications platform. 315 paths, 471 operations, 57 tags, 259 schemas. - Production base URL: `https://api.alianza.com` - Beta / integration base URL: `https://api.b2.alianza.com` - Version: v2 (URI-path versioned; every operation sits under `/v2`) ## Specs - [OpenAPI 3.0.3 (current)](https://developer.alianza.com/openapi.yaml): the live, maintained description. - [Swagger 2.0 (deprecated)](https://api.alianza.com/v2/apidocs/swagger.json): explicitly labelled outdated by Alianza; no further updates. ## Authentication - Scheme: `apiKey` in header, `X-AUTH-TOKEN`, applied globally to the whole document. - Obtain the token: `POST /v2/authorize` (operationId `logUserIn`) with admin-portal username and password; read `authToken` from the response. - Credentials are issued by an Alianza account manager. There is no self-service sign-up and no OAuth client-credentials flow for API access. - SAML/OAuth SSO exists for administrative login only (`/v2/authn/sso/*`, `/v2/authorize/sso`), not for API authorization. - Log out: `PUT /v2/authorize/logout`. Re-authorize on a 401 `Expired Auth Token`. ## Docs - [Developer portal](https://developer.alianza.com/home) - [API reference (Swagger UI)](https://developer.alianza.com/provisioning-api) - [Web services and datafeed access](https://developer.alianza.com/web-services-datafeed-access): base URLs, authentication, SFTP datafeeds. - [API guides](https://developer.alianza.com/api-guides): PDF guides for Account Create, SIP Trunking, Specialty Lines, BeYOC and Phone Numbers. - [API certification process](https://developer.alianza.com/certification-process): required before production access. - [Status page](https://status.alianza.com/): Atlassian Statuspage, SSO-gated to service-provider customers. ## Capability areas - Account and partition orchestration — `Account`, `Partition`, `Account User`, `Account Prevalidate` - End users and groups — `End User`, `User Groups`, `Management User`, `Security Groups` - Devices — `Account Device`, `Account Device Line`, `Device Inventory Management`, `Edge Node` - Telephone numbers and porting — `Telephone Number`, `Port`, `Dynamic Inventory`, `Rate Center Inventory`, `Supported Rate Centers`, `Local Calling Areas`, `Service Activation` - Business voice — `Business Line`, `Business Line Hunt Group`, `Call Group`, `Paging Group`, `Pickup Group`, `Call Parking Spot`, `IVR`, `Specialty Line` - SIP — `SIP Trunk`, `SIP Trunk Group`, `Sip Trunk Caller ID Mapping` - Voicemail and fax — `Voicemail Box`, `Voicemail Message`, `Virtual Fax`, `Virtual Fax Line`, `Media` - Plans and products — `Calling Plan`, `Calling Plan Product`, `Inbound Rate Plan Product`, `Cymbus User Product` - Usage and reporting — `CDRs`, `Report`, `Asynchronous JOB Tracker`, `Bulk Operation Collection`, `Bulk Operation Job` - Identity and branding — `Authorize`, `Single Sign On - SSO`, `SSO Configuration`, `SSO Authentication`, `SSO Exemptions`, `Brand Settings` - Compliance — `Emergency Notification`, `Address`, `Document Repository` ## Conventions - Content type: `application/json` (CSV and multipart on report/media operations). - Resource shape: `/v2/partition/{partitionId}/account/{accountId}//{resourceId}` — nearly every operation is partition-scoped. - Errors: vendor envelope `PublicApiException` — `{"status": int, "messages": [string], "data": {}}`. **Not** RFC 9457 problem+json. - Idempotency: **not supported.** No `Idempotency-Key` header exists. Treat every POST as unsafe to retry; re-query before re-creating. - Pagination: partial and inconsistent — `firstResultIndex`/`maxResult` (default 0/20) on 8 operations, `pageNum`/`pageSize` (default 0/100) on 2. Most collections are returned in full. - Rate limits: none published. No 429 response and no RateLimit headers are declared. - Async work: `202 Accepted` on 33 operations, then poll `GET /v2/job/{jobId}` and collect via `/v2/job/{jobId}/output`. - Deprecation: 50 operations carry the OpenAPI `deprecated` flag. No RFC 8594 Sunset header and no removal dates are published — diff the description to detect retirement. Replacements often ship as a `_2`/`_3` path suffix. - CDR bulk delivery: SFTP, `sftp://datafeed.alianza.com` port 10022 (Beta `sftp://datafeed.b2.alianza.com:10022`). ## What Alianza does not publish Recorded so an agent does not go looking: - No client SDK in any registry (npm, PyPI, RubyGems, Packagist, NuGet, crates.io, Maven Central all checked). - No CLI, no embedded UI component library. - No MCP server and no GraphQL endpoint. - No A2A agent card at `/.well-known/agent-card.json` or `/.well-known/agent.json`. - No `/.well-known/` documents at all — no `security.txt`, no `openid-configuration`, no `api-catalog`. - No AsyncAPI document and no customer-facing webhook catalog. - No public API changelog or release notes; platform news is published as press releases. - No public SLA and no published compliance/certification program (no trust center). - No public Postman collection. ## API Evangelist artifacts Derived and probed artifacts for this provider live at https://github.com/api-evangelist/alianza - `openapi/alianza-openapi-original.yml` — harvested OpenAPI 3.0.3 - `openapi/alianza-apidocs-swagger2-original.json` — harvested legacy Swagger 2.0 - `authentication/alianza-authentication.yml` — auth profile - `conventions/alianza-conventions.yml` — cross-cutting semantics - `errors/alianza-problem-types.yml`, `errors/alianza-error-codes.yml` — error catalog and the BrandError registry - `lifecycle/alianza-lifecycle.yml` — versioning, 50 deprecated operations, status page - `data-model/alianza-data-model.yml` — 215 entities, 307 relationships - `mcp/alianza-mcp.yml`, `mcp/alianza-tool-crosswalk.yml` — candidate MCP tools bound to real operationIds - `skills/` — five packaged agent skills for the marquee provisioning flows - `sandbox/alianza-sandbox.yml` — environments and the certification gate - `conformance/alianza-conformance.yml` — standards conformance - `security/alianza-domain-security.yml` — TLS/HSTS/DNSSEC/CAA/SPF/DMARC probe - `agentic-access/alianza-agentic-access.yml` — per-operation agentic execution contracts ## Company - [Website](https://www.alianza.com/) - [Blog](https://www.alianza.com/blog/) - [GitHub](https://github.com/alianza-dev) - [Terms of Use](https://www.alianza.com/terms-of-use/) - [Privacy Policy](https://www.alianza.com/privacy-policy/) - [Contact](https://www.alianza.com/contact-us/)