---
title: Endpoints & Regions
url: https://docs.kaltura.com/docs/getting-started/general/api-endpoints-regions
---

## Endpoints & Regions

Kaltura operates across 6 regional deployments. Each region provides the full API and service stack. Your account is provisioned to a specific region — use the corresponding endpoints.

### Regions

| Region | Code | API Base URL |
|--------|------|-------------|
| US (default) | `nvp1` | `https://www.kaltura.com/api_v3` |
| Frankfurt (DE) | `frp2` | `https://api.de.kaltura.com/api_v3` |
| Ireland (EU) | `irp2` | `https://api.eu.kaltura.com/api_v3` |
| Singapore | `sgp2` | `https://api.sg.kaltura.com/api_v3` |
| Canada | `cap2` | `https://api.ca.kaltura.com/api_v3` |
| Australia | `syp2` | `https://api.ap.kaltura.com/api_v3` |

### URL Patterns

Every Kaltura service follows a dual-naming convention — an env-coded domain and a friendly alias that resolve to the same backend:

- **env-coded:** `{service}.{regionCode}.ovp.kaltura.com` (e.g., `api.frp2.ovp.kaltura.com`)  
- **Friendly:** `{service}.{regionPrefix}.kaltura.com` (e.g., `api.de.kaltura.com`)  
- **US region:** Also supports the env-coded pattern (`www.nvp1.ovp.kaltura.com`), but the friendly aliases (`www.kaltura.com`) are more common. Note: in the US region, the Core API service name is `www` rather than `api` (e.g., `www.nvp1.ovp.kaltura.com/api_v3`).  
- **Microservices** follow the same `{svc}.{code}.ovp.kaltura.com` pattern in all regions, including US (`{svc}.nvp1.ovp.kaltura.com`).

### Service Endpoints by Category

| Category | US Endpoint | Regional Pattern |
|----------|------------|-----------------|
| **Core API** | `www.kaltura.com/api_v3` (also `www.nvp1.ovp.kaltura.com/api_v3`) | `api.{region}.kaltura.com/api_v3` (env-coded: `api.{code}.ovp.kaltura.com/api_v3`) |
| **VOD Delivery** | `cfvod.kaltura.com` | `cfvod.{code}.ovp.kaltura.com` |
| **Live Delivery** | `cflive.kaltura.com` | `cflive.{code}.ovp.kaltura.com` |
| **Analytics** | `analytics.kaltura.com` | `analytics.{region}.kaltura.com` |
| **Upload** | `upload.kaltura.com` | `upload.{code}.ovp.kaltura.com` |
| **Push/Messaging** | `push.kaltura.com` | `push.{code}.ovp.kaltura.com` |
| **Microservices** | `{svc}.nvp1.ovp.kaltura.com` | `{svc}.{code}.ovp.kaltura.com` |

Microservices include: `chat`, `connectors`, `user`, `app-registry`.  
AI services (Agents Manager, Conversational AI) follow the same microservice pattern: `agents-manager.{code}.ovp.kaltura.com`, `genie.{code}.ovp.kaltura.com`.

### Protocols & Ports

| Protocol | Port | Usage |
|----------|------|-------|
| HTTPS | 443 | All API and delivery traffic (required) |
| HTTP | 80 | Legacy fallback (US only); use HTTPS for all production traffic |
| RTMP | 1935 | Live stream ingress |
| RTMPS | 443 | Encrypted live stream ingress |
| SRT | 7045 | Low-latency live stream ingress |

**Key considerations:**  
- **Use domain names, not IP addresses** — cloud infrastructure IPs change frequently.  
- **All traffic is outbound** — firewalls need egress rules to these endpoints, not inbound.  
- **Set `$KALTURA_SERVICE_URL`** to your region's API base URL. All guides use this variable.