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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
GSMA

GSMA CAMARA Mobile Device Identifier

GSMA CAMARA Mobile Device Identifier from GSMA — 2 path(s) described in OpenAPI.

Documentation Provider Profile APIs.io OpenAPI GitHub

GSMA CAMARA Mobile Device Identifier is one of 18 APIs that GSMA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 12 schemas. It is described by OpenAPI 3.0.3, at version 0.2.0.

Requests are made against a single base URL, {apiRoot}/device-identifier/v0.2.

2 operations 2 paths 12 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.2.0
Base URL
https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
Authentication
OpenID Connect
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

GSMA CAMARA Mobile Device Identifier declares 1 security scheme for authenticating requests. It supports OpenID Connect (openId) discovered at .well-known/openid-configuration.

  • openId — Common security scheme for all CAMARA APIs

Paths & Operations 2

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

Get Device Identifiers 2

Retrieve details about the device being used by a mobile subscriber

POST
/retrieve-identifier
Get details about the specific device being used by a given mobile subscriber
retrieveIdentifier 1 param body → 200400401403404422429
POST
/retrieve-type
Get details about the type of device being used by a given mobile subscriber
retrieveType 1 param body → 200400401403404422429

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Device (4 properties), DeviceIpv4Addr (3 properties), DeviceType (3 properties), ErrorInfo (3 properties). Each schema is shown below with its type and property counts.

LastChecked
object
The last time that the information returned (e.g. IMEI) was confirmed to be correct by the mobile operator for the provided identifier (e.g. phone number)
1 property
DeviceIdentifier
object
The individual physical mobile device identifier, as expressed by the IMEI and IMEISV
2 properties
DeviceType
object
The physical device type, as expressed by Type Approval Code, manufacturer name and model name
3 properties
Device
object
End-user equipment able to connect to a mobile network. Examples of devices include smartphones or IoT sensors/actuators. The developer can choose to provide t…
4 properties
DeviceIpv4Addr
object
The device should be identified by either the public (observed) IP address and port as seen by the application server, or the private (local) and any public (o…
3 properties
ErrorInfo
object
Common CAMARA error response object
3 properties 3 required
NetworkAccessIdentifier
string
A public identifier addressing a subscription in a mobile network. In 3GPP terminology, it corresponds to the GPSI formatted with the External Identifier ({Loc…
PhoneNumber
string
A public identifier addressing a telephone subscription. In mobile networks it corresponds to the MSISDN (Mobile Station International Subscriber Directory Num…
Port
integer
TCP or UDP port number
RequestBody
object
Common request body to allow optional Device object to be passed
1 property
SingleIpv4Addr
string
A single IPv4 address with no subnet mask
DeviceIpv6Address
string
The device should be identified by the observed IPv6 address, or by any single IPv6 address from within the subnet allocated to the device (e.g. adding ::0 to…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gsma-open-gateway-device-identifier-openapi.yml Raw ↑

Other APIs GSMA publishes across the network.

GSMA Mobile Money API
AE Profile APIs.io
GSMA Call Forwarding Signal
AE Profile APIs.io
GSMA Carrier Billing
AE Profile APIs.io
GSMA Carrier Billing Refund
AE Profile APIs.io
GSMA Device Location Retrieval
AE Profile APIs.io
GSMA Device Location Verification
AE Profile APIs.io
GSMA Device Reachability Status
AE Profile APIs.io
GSMA Device Roaming Status
AE Profile APIs.io
GSMA Device Swap
AE Profile APIs.io
GSMA Home Devices QoD
AE Profile APIs.io
GSMA Know Your Customer Match
AE Profile APIs.io
GSMA Number Verification
AE Profile APIs.io
← Back to G APIs
API Details
ID
gsma:gsma-open-gateway-device-identifier-openapi
Base URL
https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
Docs
https://developer.mobilemoneyapi.io/api-versions-1.2/
Provider
GSMA
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=gsma-open-gateway-device-identifier-openapi&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/gsma-open-gateway-device-identifier-openapi"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of GSMA CAMARA Mobile Device Identifier, 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.