Telenor Sverige Usage Consumption API

The UsageConsumption API from Telenor Sverige — 1 operation(s) for usageconsumption.

Operations 1

GET /api/usageConsumption/v1/subscription/{msisdn} Gets subscription usage consumption #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/telenor-sverige:telenor-sverige-usageconsumption-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

telenor-sverige-usageconsumption-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Mobile Subscriptions Administration Usage Consumption API
  description: 'Provides a corporate information model, generic for SME and Large. Used for agreement details for existing customers as creating new agreements or subscriptions.

    This is an API intended for software developers and system integrators implementing client applications for handling order B2B segment. It is assumed that the reader is familiar with software API concepts such as REST, JSON and OpenAPI interface specification OpenAPI Specification.


    Response Codes

    This API follows standard response codes for REST APIs please refer to W3C response codes'
  termsOfService: https://www.telenor.se/foretag/kundservice/villkor-prislistor-och-blanketter/villkor/allmanna-villkor/
  contact:
    name: Telenor Support
    url: https://www.telenor.se/foretag/kundservice/
    email: ''
  version: 1.80.0
servers:
- url: https://apis.telenor.se/
  description: Production environment
tags:
- name: UsageConsumption
paths:
  /api/usageConsumption/v1/subscription/{msisdn}:
    get:
      tags:
      - UsageConsumption
      summary: Gets subscription usage consumption
      operationId: UsageConsumption_UsageByMsisdn
      parameters:
      - name: X-Transaction-Id
        in: header
        description: Transaction id defined by calling system could be for instance Epoch time
        schema:
          type: string
        example: '1580371581117'
      - name: msisdn
        in: path
        description: Phone number
        required: true
        schema:
          type:
          - string
          - 'null'
          description: Swedish mobile number
          example: '46701740605'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CoreApi.UsageConsumption.SubscriptionUsageConsumptionView'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CoreApi.Common.ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CoreApi.Common.ErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CoreApi.Common.ErrorResponse'
      security:
      - bearer-access-token: []
components:
  schemas:
    CoreApi.UsageConsumption.UsageConsumptionView:
      type: object
      properties:
        Id:
          type:
          - string
          - 'null'
        Cost:
          type:
          - string
          - 'null'
        Duration:
          type:
          - string
          - 'null'
        Volume:
          type:
          - string
          - 'null'
        Calls:
          type:
          - string
          - 'null'
      additionalProperties: false
    CoreApi.UsageConsumption.SubscriptionUsageConsumptionView:
      type: object
      properties:
        PhoneNumber:
          type:
          - string
          - 'null'
        BillingPeriod:
          type:
          - string
          - 'null'
        Usage:
          type:
          - array
          - 'null'
          items:
            $ref: '#/components/schemas/CoreApi.UsageConsumption.UsageConsumptionView'
      additionalProperties: false
    CoreApi.Common.ErrorResponse:
      type: object
      properties:
        ErrorMessage:
          type:
          - string
          - 'null'
        ErrorCode:
          type: integer
          format: int32
      additionalProperties: false
x-provenance:
  method: harvested
  publisher: Telenor Sverige
  source: https://developer.telenor.se/mobile-order/openapi
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)