AT&T Device Management API
The Device Management API from AT&T — 2 operation(s) for device management.
The Device Management API from AT&T — 2 operation(s) for device management.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/att-device-management-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: AT&T MVNX Device Management API
description: TM Forum-aligned API suite for Mobile Virtual Network Operators (MVNOs) using AT&T's network infrastructure. Provides subscriber activation, number management, porting operations, device and SIM management, subscriber profile management, service lifecycle management, and balance/policy management. Follows TMF Open API standards including TMF 622, 637, 639, 640, 654, 674, 689, 702, 716, and 761.
version: 4.0.0
contact:
url: https://devex-web.att.com/mvnx/docs/mvnx-contact-us
x-generated-from: documentation
x-last-validated: '2026-04-19'
servers:
- url: https://devex-web.att.com
description: AT&T Developer Experience API Gateway
tags:
- name: Device Management
paths:
/resource:
get:
operationId: listResources
summary: AT&T List Devices and SIMs
description: Retrieve device details and SIM information for subscribers. Corresponds to TMF 639 Resource Inventory API.
tags:
- Device Management
parameters:
- name: relatedParty.id
in: query
required: false
description: Filter resources by subscriber ID
schema:
type: string
example: sub-a1b2c3d4
responses:
'200':
description: Resources successfully retrieved
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/Resource'
examples:
ListResources200Example:
summary: Default listResources 200 response
x-microcks-default: true
value:
- id: resource-500123
name: Samsung Galaxy S25
resourceType: device
status: active
serialNumber: IMEI-123456789012345
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
/resource/{id}:
get:
operationId: getResource
summary: AT&T Get Device or SIM Status
description: Retrieve the current status and details of a specific device or SIM card. Corresponds to TMF 639 Resource Inventory API.
tags:
- Device Management
parameters:
- name: id
in: path
required: true
description: Resource (device or SIM) ID
schema:
type: string
example: resource-500123
responses:
'200':
description: Resource details retrieved
content:
application/json:
schema:
$ref: '#/components/schemas/Resource'
examples:
GetResource200Example:
summary: Default getResource 200 response
x-microcks-default: true
value:
id: resource-500123
name: Samsung Galaxy S25
resourceType: device
status: active
serialNumber: IMEI-123456789012345
'404':
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
patch:
operationId: updateResource
summary: AT&T Update Resource (Reset Voicemail Password)
description: Update a resource attribute, such as resetting the voicemail password for a subscriber's device. Corresponds to TMF 702 Resource Activation and Configuration API.
tags:
- Device Management
parameters:
- name: id
in: path
required: true
description: Resource ID
schema:
type: string
example: resource-500123
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/ResourceUpdate'
examples:
UpdateResourceRequestExample:
summary: Default updateResource request
x-microcks-default: true
value:
resourceCharacteristic:
- name: voicemailPassword
value: '1234'
responses:
'200':
description: Resource successfully updated
content:
application/json:
schema:
$ref: '#/components/schemas/Resource'
examples:
UpdateResource200Example:
summary: Default updateResource 200 response
x-microcks-default: true
value:
id: resource-500123
status: active
'404':
description: Resource not found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
components:
schemas:
ResourceUpdate:
type: object
properties:
resourceCharacteristic:
type: array
items:
type: object
properties:
name:
type: string
description: Characteristic name to update
example: voicemailPassword
value:
type: string
description: New value for the characteristic
example: '1234'
ErrorResponse:
type: object
properties:
code:
type: string
description: Error code
example: '400'
reason:
type: string
description: Short reason for the error
example: Bad Request
message:
type: string
description: Detailed error message
example: Invalid input parameter value
status:
type: string
description: HTTP status code
example: '400'
Resource:
type: object
properties:
id:
type: string
description: Unique resource identifier
example: resource-500123
name:
type: string
description: Device or SIM name
example: Samsung Galaxy S25
resourceType:
type: string
description: Type of resource
enum:
- device
- sim
example: device
status:
type: string
description: Resource operational status
enum:
- active
- inactive
- suspended
example: active
serialNumber:
type: string
description: Device IMEI or SIM ICCID
example: IMEI-123456789012345
securitySchemes:
clientId:
type: apiKey
in: header
name: X-Client-Id
description: Client ID enforcement policy for MVNX API authentication