canonical: https://jentic.com/apis/telenorconnexion.com/telenorconnexion

# Telenor Connexion Managed IoT Cloud REST API

REST API for Telenor Connexion's Managed IoT Cloud (MIC) platform. Provides endpoints for authentication, thing management, thing types, and data reporting. The API exposes 6 endpoints secured with apiKey, bearer authentication.

## For AI agents

Programmatically authenticate user, create a thing type. Covers 6 operations with apiKey, bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Authenticate user
- Create a thing type
- Get thing details
- Report data to a thing
- Monitor Telenor Connexion Managed IoT Cloud REST API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Telenor Connexion Managed IoT Cloud REST API to perform identity auth operations programmatically. The API provides 6 endpoints covering core functionality including authenticate user, create a thing type, create a thing.

Example prompt: Call POST `/auth/login` to authenticate user

### Automated Authentication Management

Automate authentication operations by combining multiple Telenor Connexion Managed IoT Cloud REST API endpoints. Agents can create a thing type and then create a thing in a single workflow.

Example prompt: Call POST /thingtypes to create a thing type, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Telenor Connexion Managed IoT Cloud REST API 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, bearer tokens manually.

Example prompt: Search Jentic for 'authenticate user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/login` | Authenticate user |
| POST | `/thingtypes` | Create a thing type |
| POST | `/things` | Create a thing |
| GET | `/things` | Get thing details |
| PUT | `/things/resources` | Report data to a thing |
| GET | `/metadata/manifest` | Get API configuration manifest |

## Key resources

- **Authentication** — User authentication and login
- **Thing Types** — Thing type (category) management
- **Things** — IoT thing management and data reporting
- **Metadata** — API configuration and manifest

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 77 / 100
- **View full report:** https://jentic.com/apis/telenorconnexion.com/telenorconnexion/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 Connexion Managed IoT Cloud REST API by hand means calling `/auth/login` for a bearer token, also carrying the x-api-key header for your MIC instance, targeting your API gateway host, and writing the token refresh and retry glue yourself. Through Jentic you install once, import the Telenor Connexion Managed IoT Cloud REST API from the API Directory, store the API key and login credentials once, and your agent calls it.
- **Permission scoping:** The Telenor Connexion Managed IoT Cloud REST API identifies things through the request body rather than the URL path, so limit the agent to the operations it needs, such as listing things or reading the metadata manifest. You choose that allowed set, and write operations like creating a thing type are not included unless you add them.
- **Credential handling:** Your Telenor Connexion API key and login credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list registered things' or 'read the metadata manifest', and Jentic returns the matching Telenor Connexion operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Telenor Connexion Managed IoT Cloud REST API use?

The Telenor Connexion Managed IoT Cloud REST API uses apiKey, bearer authentication. 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 authenticate user with the Telenor Connexion Managed IoT Cloud REST API?

Yes. Use the POST `/auth/login` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Telenor Connexion Managed IoT Cloud REST API?

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 authenticate user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate user'. Jentic returns the matching Telenor Connexion Managed IoT Cloud REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Telenor Connexion Managed IoT Cloud REST API have?

The Telenor Connexion Managed IoT Cloud REST API exposes 6 endpoints covering authentication, thing types, things operations.

### Can I limit what my agent is allowed to do with the Telenor Connexion Managed IoT Cloud REST API?

Yes. Jentic One runs self-hosted, so you decide which of the six operations your agent may call and which credentials it may use. You can restrict it to read-only calls such as GET /things to list thing details or GET `/metadata/manifest` to read the configuration manifest, and leave out write operations like POST /thingtypes or POST /things. Because this API identifies things through the request body rather than the URL path, the allowed operation set you configure is what bounds the agent.