National Australia Bank Device Operations API
The Device Operations API from National Australia Bank — 1 operation(s) for device operations.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/national-australia-bank:national-australia-bank-device-operations-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
openapi: 3.2.0
info:
description: All CyberSource API specs merged together. These are available at https://developer.cybersource.com/api/reference/api-reference.html
version: 0.0.1
title: CyberSource Merged Spec Device Operations API
servers:
- url: https://apitest.cybersource.com/
tags:
- name: Device Operations
paths:
/dms/v2/device-transfer:
post:
summary: Device Transfer
description: Allows transferring of devices within the hierarchy. Both 'Active' and 'Inactive' devices can be transferred.
tags:
- Device Operations
operationId: postTransferTerminalAssociation
responses:
'201':
description: Moved all device(s) to their respective destination(s)
content:
application/json;charset=UTF-8:
schema:
type: array
description: A collection of details of each device transfer
items:
type: object
properties:
status:
type: string
enum:
- CREATED
- ACCEPTED
details:
type: array
items:
type: object
properties:
field:
type: string
example: 73c7d8ba-3673-4baf-801e-cf4bf5cc2b57
reason:
type: string
example: Device successfully assigned to organizationId/merchantId.
code:
type: string
example: deviceTransfer.sync.success
'206':
description: Partial Success. Moved device(s) to their respective destination(s)
content:
application/json;charset=UTF-8:
schema:
type: array
description: A collection of details of each device transfer
items:
type: object
properties:
status:
type: string
enum:
- CREATED
- ACCEPTED
- BAD_REQUEST
details:
type: array
items:
type: object
properties:
field:
type: string
example: 73c7d8ba-3673-4baf-801e-cf4bf5cc2b57
reason:
type: string
example: Device successfully assigned to organizationId/merchantId.
code:
type: string
example: deviceTransfer.async.success
'400':
description: Bad Request
content:
application/json;charset=UTF-8:
schema:
type: object
properties:
status:
type: string
description: The status of the submitted request.
enum:
- BAD_REQUEST
message:
type: string
description: The detail message related to the status and reason listed above.
code:
type: string
description: An optional short string which identifies the exact error.
details:
type: array
description: An optional array which provides more details of the error.
items:
type: object
properties:
field:
type: string
description: This is the flattened JSON object field name/path that is either missing or invalid.
reason:
type: string
description: 'Possible reasons for the error.
'
code:
type: string
description: An optional short string which identifies the exact field error.
submitTimeUtc:
type: string
description: 'Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ`
Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the
time. The Z indicates UTC.
'
'401':
description: Unauthorized
content:
application/json;charset=UTF-8:
schema:
type: object
properties:
status:
type: string
description: 'The status of the submitted request.
'
enum:
- UNAUTHORIZED
message:
type: string
description: The detail message related to the status and reason listed above.
code:
type: string
description: An optional short string which identifies the exact error.
submitTimeUtc:
type: string
description: 'Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ`
Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the
time. The Z indicates UTC.
'
'403':
description: Forbidden
content:
application/json;charset=UTF-8:
schema:
type: object
properties:
status:
type: string
description: 'The status of the submitted request.
'
enum:
- FORBIDDEN
message:
type: string
description: The detail message related to the status and reason listed above.
code:
type: string
description: An optional short string which identifies the exact error.
submitTimeUtc:
type: string
description: 'Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ`
Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the
time. The Z indicates UTC.
'
'404':
description: Not Found
content:
application/json;charset=UTF-8:
schema:
type: object
properties:
status:
type: string
description: 'The status of the submitted request.
'
enum:
- NOT_FOUND
message:
type: string
description: The detail message related to the status and reason listed above.
code:
type: string
description: An optional short string which identifies the exact error.
submitTimeUtc:
type: string
description: 'Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ`
Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the
time. The Z indicates UTC.
'
'500':
description: Unexpected system error or system timeout.
content:
application/json;charset=UTF-8:
schema:
type: object
properties:
status:
type: string
description: 'The status of the submitted request.
'
enum:
- INTERNAL_SERVER_ERROR
message:
type: string
description: The detail message related to the status and reason listed above.
code:
type: string
description: An optional short string which identifies the exact error.
submitTimeUtc:
type: string
description: 'Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ`
Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the
time. The Z indicates UTC.
'
x-example:
example0:
summary: Transfer a device based on its deviceId and merchantId.
value:
deviceId: 2a63a895-a3a7-415a-9a65-47107a1543b6
merchantId: CYBSNYStore
example1:
summary: Transfer a device based on its deviceId and destination orgId(account).
value:
deviceId: 2a63a895-a3a7-415a-9a65-47107a1543b6
organizationId: CYBSNYStore_acct
example2:
summary: Transfer a device based on its deviceId and destination orgId(merchant).
value:
deviceId: 2a63a895-a3a7-415a-9a65-47107a1543b6
organizationId: CYBSLondonStore
example3:
summary: Transfer a device based on its deviceId and destination orgId. If the request contains both merchantId and organizationId, then organizationId will be given higher preference.
value:
deviceId: 2a63a895-a3a7-415a-9a65-47107a1543b6
organizationId: CYBSUnitedKingdomReseller
merchantId: CYBSLondonStore
requestBody:
content:
application/json;charset=UTF-8:
schema:
type: array
items:
type: object
required:
- deviceId
properties:
deviceId:
type: string
description: ID of the device to be transferred.
maxLength: 256
merchantId:
type: string
description: A field representing the merchant to which the device has to be transferred.
maxLength: 30
organizationId:
type: string
description: A field representing value of either merchant, account or portfolio. It has a higher priority than merchantId, and will be preferred if request contains both merchantId and organizationId.
maxLength: 30
description: deviceId that has to be transferred along with the destination organizationId or merchantId. Any one of organizationId or merchantId is required alongside deviceId for a valid transfer request.
required: true