canonical: https://jentic.com/apis/telenor.no/telenor-no

# Telenor No Telenor APIs

Telenor telecommunications and business services APIs including mobile and fixed network ordering, IoT management, SMS messaging, positioning services, CDN, and service ticket management for Norwegian telecommunications infrastructure. The API exposes 18 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create mobile subscription, list mobile subscriptions. Covers 18 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Create mobile subscription
- List mobile subscriptions
- Get mobile subscription
- Update mobile subscription
- Monitor Telenor APIs operational status and events

## Use cases

### Communications Operations

Use the Telenor APIs to perform communications operations programmatically. The API provides 18 endpoints covering core functionality including create mobile subscription, list mobile subscriptions, get mobile subscription.

Example prompt: Call POST `/mobile-order/v1/subscriptions` to create mobile subscription

### Automated Broadband Offer Management

Automate broadband offer operations by combining multiple Telenor APIs endpoints. Agents can list mobile subscriptions and then get mobile subscription in a single workflow.

Example prompt: Call GET `/mobile-order/v1/subscriptions` to list mobile subscriptions, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Telenor APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create mobile subscription', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/mobile-order/v1/subscriptions` | Create mobile subscription |
| GET | `/mobile-order/v1/subscriptions` | List mobile subscriptions |
| GET | `/mobile-order/v1/subscriptions/{subscriptionId}` | Get mobile subscription |
| PATCH | `/mobile-order/v1/subscriptions/{subscriptionId}` | Update mobile subscription |
| POST | `/fixed-order/v1/orders` | Create fixed network order |
| GET | `/fixed-order/v1/orders` | List fixed network orders |
| GET | `/iot-order/v1/subscriptions` | List IoT subscriptions |
| PATCH | `/iot-order/v1/subscriptions` | Update IoT subscription |

## Key resources

- **Broadband Offer** — Operations related to Broadband Offer
- **Fixed Order** — Operations related to Fixed Order
- **IoT Order** — Operations related to IoT Order
- **IoT Positioning** — Operations related to IoT Positioning
- **Mobile Order** — Operations related to Mobile Order

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/telenor.no/telenor-no/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Telenor APIs by hand means provisioning its API key, attaching that header to every call against api.telenor.no, and building the paging and retry handling across mobile, fixed, and IoT order endpoints yourself. Through Jentic you install once, import the Telenor APIs from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Telenor APIs put the subscription id in the URL path (`/mobile-order/v1/subscriptions/{subscriptionId}`), so a rule can pin your agent to one subscription: it can read and patch that subscription and nothing else. You choose the operations it may call, so ones like placing a new order are not included unless you add them.
- **Credential handling:** Your Telenor API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list mobile subscriptions' or 'update a subscription', and Jentic returns the matching Telenor operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Telenor APIs use?

The Telenor APIs uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create mobile subscription with the Telenor APIs?

Yes. Use the POST `/mobile-order/v1/subscriptions` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Telenor APIs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create mobile subscription through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create mobile subscription'. Jentic returns the matching Telenor APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Telenor APIs have?

The Telenor APIs exposes 18 endpoints covering broadband offer, fixed order, iot order operations.

### Can I limit what my agent is allowed to do with the Telenor APIs?

Yes. Because you run Jentic One yourself, your own rules decide which Telenor operations and credentials the agent may use, so you can allow just the ones it needs, such as GET and PATCH on `/mobile-order/v1/subscriptions/{subscriptionId}` to read and update a subscription, while leaving out operations like POST `/mobile-order/v1/subscriptions` or POST `/fixed-order/v1/orders` that place new orders. Since the subscription id sits in the URL path, a rule can pin the agent to a single subscription so it touches that one and nothing else. The agent only ever sees the operations you grant, and your encrypted API key is injected at execution time rather than exposed to it.