How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

KORE Wireless Session API

Customers of KORE having Radius Accounting integrated at carrier level will have session events collected at KORE. Session START and STOP events are correlated, and data is exposed as Session API for consumption. This API also provides the session count for any duration within the last 7 days.Typical use cases would be 1) UI showing recent sessions against a subscription-id or iccid or msisdn in a paginated fashion. 2) Fetch session count so to generate alarms when a defined threshold is crossed.

KORE Wireless Session API is one of 35 APIs that KORE Wireless publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Session. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.korewireless.com/connectivity.

2 operations 2 paths 0 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.korewireless.com/connectivity
Authentication
API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 2

KORE Wireless Session API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (api_key). It supports OAuth 2.0 (Auth) using the clientCredentials flow. By default, every request must be authenticated, though some operations may also be called without credentials.

  • Auth — token expiry is given in seconds

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Session 2

Customers of KORE having Radius Accounting integrated at carrier level will have session events collected at KORE. Session START and STOP events are correlated, and data is expose…

GET
/v1/accounts/{account-id}/sessions
Get Session Details
9 params → 200400401403404409500502
GET
/v1/accounts/{account-id}/in-session
Get Session Status
4 params → 200400401403404500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kore-wireless-session-api-openapi.yml Raw ↑

Other APIs KORE Wireless publishes across the network.

KORE Wireless Account API
KORE Wireless Accounts API
KORE Wireless Activation Profiles API
KORE Wireless Alerting API
KORE Wireless Auth API
KORE Wireless Clients API
KORE Wireless Commands Resource API
KORE Wireless DataSessions Resource API
KORE Wireless Diagnostics API
KORE Wireless Eligibility API
KORE Wireless eSIM Profile Management API
KORE Wireless Health API
Where this information came from

This is an independent, third-party profile of KORE Wireless Session API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.