National Australia Bank User Management API
The User Management API from National Australia Bank — 1 operation(s) for user management.
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-user-management-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 User Management API
servers:
- url: https://apitest.cybersource.com/
tags:
- name: User Management
paths:
/ums/v1/users:
get:
deprecated: true
summary: Get User Information - Deprecated
description: This endpoint is deprecated. Please use the search end point.
tags:
- User Management
operationId: getUsers
x-queryParameterDefaults:
organizationId: testrest
permissionId: CustomerProfileViewPermission
parameters:
- in: query
name: organizationId
description: This is the orgId of the organization which the user belongs to.
schema:
type: string
- in: query
name: userName
description: User ID of the user you want to get details on.
schema:
type: string
- in: query
name: permissionId
description: permission that you are trying to search user on.
schema:
type: string
- in: query
name: roleId
description: role of the user you are trying to search on.
schema:
type: string
responses:
'200':
description: OK
content:
application/hal+json;charset=utf-8:
schema:
type: object
title: umsV1UsersGet200Response
properties:
users:
type: array
items:
type: object
properties:
accountInformation:
type: object
properties:
userName:
type: string
roleId:
type: string
permissions:
type: array
items:
type: string
description: array of permissions
status:
type: string
description: 'Valid values:
- active
- inactive
- locked
- disabled
- forgotpassword
- deleted
'
createdTime:
type: string
format: date-time
lastAccessTime:
type: string
format: date-time
languagePreference:
type: string
timezone:
type: string
organizationInformation:
type: object
properties:
organizationId:
type: string
contactInformation:
type: object
properties:
email:
type: string
phoneNumber:
type: string
firstName:
type: string
lastName:
type: string
customFields:
type: object
additionalProperties:
type: string
example:
users:
- accountInformation:
userName: auto_nonmember
roleId: admin
permissions:
- ReportViewPermission
- ReportGeneratePermission
status: active
createdTime: '2018-06-14T19:45:52.093Z'
lastAccessTime: '2018-06-14T19:45:52.093Z'
languagePreference: en-US
timezone: America/Los_Angeles
organizationInformation:
organizationId: auto_nonmember
contactInformation:
email: auto_nonmember@exchange.com
phoneNumber: '4445551234'
firstName: Zeta
lastName: DMH
customFields:
employeeId: '12344'
employeeName: John Doe
employeeDesignation: abc
zone: NA
department: map
'400':
description: Invalid request.
content:
application/hal+json;charset=utf-8:
schema:
type: object
title: umsV1UsersGet400Response
properties:
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.
Returned by Cybersource for all services.
'
status:
type: string
description: "The status of the submitted transaction.\n\nPossible values:\n - INVALID_REQUEST\n"
reason:
type: string
description: "The reason of the status.\n\nPossible values:\n - MISSING_FIELD\n - INVALID_DATA\n - DUPLICATE_REQUEST\n - INVALID_CARD\n - INVALID_MERCHANT_CONFIGURATION\n - INVALID_AMOUNT\n - CAPTURE_ALREADY_VOIDED\n - ACCOUNT_NOT_ALLOWED_CREDIT\n - NOT_SUPPORTED\n"
message:
type: string
description: The detail message related to the status and reason listed above.
details:
type: array
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.\n\nPossible values:\n - MISSING_FIELD\n - INVALID_DATA\n"
'500':
description: Unexpected server error.