Telenor No Telenor APIs
63
AI ReadinessAI-Aware (B)63/100
Official vendor OpenAPI document · agent-readyCommunicationsSms MessagingapiKey18 EndpointsREST
For Agents
Programmatically create mobile subscription, list mobile subscriptions. Covers 18 operations with apiKey authentication.
Use for: I need to mobile subscription, I want to mobile subscriptions, Search for mobile subscription, Find all mobile subscription
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
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.
Install Jentic One Beta
Connect the Telenor APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Telenor APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftelenor.no%2Ftelenor-no" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftelenor.no%2Ftelenor-no" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Telenor APIs.
Create mobile subscription
List mobile subscriptions
Get mobile subscription
Update mobile subscription
Monitor Telenor APIs operational status and events
Use Cases
Patterns agents use Telenor APIs for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'create mobile subscription', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
18 endpoints — 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.
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
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
Jentic AI Readiness Score
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.
T
Telenor APIs
- AI-Aware (B)63/100
93
Foundational Compliance57
Developer Experience & Jentic Compatibility45
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
29%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
45
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
20%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Telenor APIs through Jentic.
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.
GET STARTED