Telenor Sverige DHCP Relay API

Endpoints for managing DHCP Relay.

Operations 3

GET /corporate/fixed-network/product-inventory-management/v1/product/dhcp-relay/{requestId} Fetches a DHCP Relay request #
POST /corporate/fixed-network/product-inventory-management/v1/product/dhcp-relay/remove Requests to remove a DHCP Relay configuration #
POST /corporate/fixed-network/product-inventory-management/v1/product/dhcp-relay Requests a new DHCP Relay configuration #

Specifications

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-wi-fi-quote-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-lan-quote-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-site-migration-quote-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-site-quote-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-quote-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-quote-group-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-service-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-access-type-with-access-speed-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-access-type-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-product-type-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-fixed-network-offer-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-service-parameter-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-service-details-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-vpn-ncmc-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-dhcp-relay-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-static-route-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-add-vpn-ncmc-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-termination-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-sid-with-provider-connection-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-account-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-sid-with-attribute-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-case-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-close-case-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-case-log-dto-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-add-contact-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-create-site-request-v2-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-safe-contact-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-update-contact-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-add-contact-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-site-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-cancellation-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-order-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-case-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-order-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-cancellation-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-list-cancellations-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-charge-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-refund-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-refund-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-charge-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/telenor-sverige/json-schema/telenor-sverige-media-type-schema.json

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-dhcp-relay-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-dhcp-relay-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Product Inventory Management DHCP Relay API
  description: 'The Product Inventory Management API provides a standardized mechanism to manage product inventory information. The API consists of a simple set of operations that interact with Inventory systems in a consistent manner.''

    ### Notifications

    When a Request is sent to the backend systems, its lifecycle state changes and an event is sent to the Event Notification API. The notification `detailedMessage` attribute will have the following content, depending on the type of request:

    #### General requests

    ```

    {

    "message": "The request is in progress.",

    "requestId": "bf13697e-ab73-4a75-bc1b-903147594d11"

    }

    ```

    #### Termination requests

    ```

    {

    "message": "The request is in progress.",

    "id": "bf13697e-ab73-4a75-bc1b-903147594d11",

    "type": "termination",

    "products": [

    {

    "productId": "SID2532144",

    "state": "IN_PROGRESS"

    }

    ]

    }'
  termsOfService: https://www.telenor.se/globalassets/mediabibliotek/telenor-foretag/pdfer/priser-och-villkor/general-terms-and-conditions-october-2012.pdf
  contact:
    name: Telenor Support
    url: https://www.telenor.se/foretag/kundservice/
  version: 2.4.17
servers:
- url: https://apis-test.telenor.se
  description: Test environment
tags:
- name: DHCP Relay
  description: Endpoints for managing DHCP Relay.
paths:
  /corporate/fixed-network/product-inventory-management/v1/product/dhcp-relay/{requestId}:
    get:
      tags:
      - DHCP Relay
      summary: Fetches a DHCP Relay request
      description: Fetches a DHCP Relay request.
      operationId: getDhcpRelayRequest
      parameters:
      - name: X-On-Behalf-Of-Org-Nr
        in: header
        description: The organization number when the request is on behalf of another party.
        schema:
          type: string
        example: 5564210309
      - name: requestId
        in: path
        required: true
        schema:
          type: string
          format: uuid
      responses:
        '200':
          description: DHCP Relay request successfully fetched.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DhcpRelayResponse'
        '400':
          description: Invocation failed because of wrong header and/or query parameters
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ErrorResponse'
  /corporate/fixed-network/product-inventory-management/v1/product/dhcp-relay/remove:
    post:
      tags:
      - DHCP Relay
      summary: Requests to remove a DHCP Relay configuration
      description: Requests to remove a DHCP Relay configuration.
      operationId: removeDhcpRelay_1
      parameters:
      - name: X-On-Behalf-Of-Org-Nr
        in: header
        description: The organization number when the request is on behalf of another party.
        schema:
          type: string
        example: 5564210309
      requestBody:
        content:
          '*/*':
            schema:
              $ref: '#/components/schemas/ConfigureDhcpRelayRequest'
      responses:
        '201':
          description: New request for removing DHCP Relay successfully created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DhcpRelayResponse'
        '400':
          description: Invocation failed because of wrong header and/or query parameters
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ErrorResponse'
  /corporate/fixed-network/product-inventory-management/v1/product/dhcp-relay:
    post:
      tags:
      - DHCP Relay
      summary: Requests a new DHCP Relay configuration
      description: Requests a new DHCP Relay configuration.
      operationId: requestDhcpRelay
      parameters:
      - name: X-On-Behalf-Of-Org-Nr
        in: header
        description: The organization number when the request is on behalf of another party.
        schema:
          type: string
        example: 5564210309
      requestBody:
        content:
          '*/*':
            schema:
              $ref: '#/components/schemas/ConfigureDhcpRelayRequest'
      responses:
        '201':
          description: New DHCP Relay request successfully created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DhcpRelayResponse'
        '400':
          description: Invocation failed because of wrong header and/or query parameters
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    DhcpRelayResponse:
      type: object
      properties:
        requestId:
          type: string
          description: A unique identifier for the request.
          format: uuid
          example: 2d5b553d-f4c2-4803-b64a-ed903e1dde0f
        productId:
          type: string
          description: The installed product ID.
          example: SID5134123
        vpnId:
          type: string
          description: ID of the VPN.
          example: '71238723'
        luNumber:
          type: string
          description: The LU Number of the CPE.
          example: '2361292'
        primaryIpHelper:
          type: string
          description: The primary DHCP server's IP address.
          example: 10.0.2.3
        secondaryIpHelper:
          type: string
          description: The secondary DHCP server's IP address.
          example: 10.0.3.3
        state:
          type: string
          description: The state in which the request is.
          example: IN_PROGRESS
          enum:
          - NEW
          - PARTIALLY_PROCESSED
          - IN_PROGRESS
          - CANCELLED
          - COMPLETED
        action:
          type: string
          description: The type of action of the original request.
          example: ADD
          enum:
          - ADD
          - REMOVE
        onBehalfOfOrgNr:
          type: string
          description: The organization number on behalf of which the request was made.
          example: '5566778899'
        createdDate:
          type: string
          description: The date and time that the request was received by the API.
          format: date-time
          example: '2019-08-24T14:15:22Z'
    ErrorResponse:
      type: object
      properties:
        message:
          type: string
          description: The reason that caused the error.
          example: The provided product offer does not exist.
        code:
          type: string
          description: An application specific error code to differentiate error responses.
          example: MISSING_REQUIRED_PARAMETER
          enum:
          - MISSING_REQUIRED_PARAMETER
          - INVALID_INPUT
          - CANCELLATION_OF_TERMINATION_NOT_POSSIBLE
          - TERMINATION_REQUEST_ALREADY_CANCELLED
          - TERMINATION_REQUEST_RETRIGGER_NOT_POSSIBLE
          - TERMINATION_OF_PRODUCT_NOT_POSSIBLE
          - TERMINATION_PRODUCTS_MUST_BELONG_TO_THE_SAME_SITE
          - INVALID_JWT
          - UNAUTHORIZED_HEADER_USAGE
          - UNAUTHORIZED
          - LAN_PORT_REQUEST_NOT_FOUND
          - STATIC_ROUTE_REQUEST_NOT_FOUND
          - DHCP_RELAY_REQUEST_NOT_FOUND
          - TERMINATION_REQUEST_NOT_FOUND
          - PRODUCT_NOT_FOUND
          - AGREEMENT_NOT_FOUND
          - AGREEMENT_STRUCTURE_NOT_FOUND
          - VPN_REQUEST_NOT_FOUND
          - SITE_NOT_FOUND
          - REQUEST_NOT_FOUND
          - TOO_MANY_REQUESTS
          - INTERNAL_ERROR
          - CLARIFY_ERROR
          - MISSING_AGREEMENT_IN_CAS
          - SALESFORCE_ERROR
        timestamp:
          type: integer
          description: The date and time using the epoch standard of when the error occurred.
          format: int64
          example: 1615292025
    ConfigureDhcpRelayRequest:
      required:
      - primaryIpHelper
      - productId
      - vpnId
      type: object
      properties:
        productId:
          type: string
          description: The installed product ID.
          example: SID5134123
        luNumber:
          type: string
          description: The LU Number of the CPE.
          example: '2361292'
        vpnId:
          type: string
          description: ID of the VPN.
          example: '71238723'
        primaryIpHelper:
          type: string
          description: The primary DHCP server's IP address.
          example: 10.0.2.3
        secondaryIpHelper:
          type: string
          description: The secondary DHCP server's IP address.
          example: 10.0.3.3
x-tagGroups:
- name: API Operations
  tags:
  - Product Inventory
  - VPN
  - Static Routes
  - DHCP Relay
  - LAN Ports
  - Termination
x-provenance:
  method: harvested
  publisher: Telenor Sverige
  source: https://developer.telenor.se/product-inventory/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)