HomeGuidesAPI ReferenceGuidesMRT APIConfiguration API
GitHubAirheads Developer Community
Guides
GitHubAirheads Developer Community

Postman Collection

Suggest Edits

Postman is a popular tool for testing APIs. HPE Aruba Networking Central provides two official Postman collections that help you test and explore REST APIs directly from Postman

  1. MRT APIs Collection
  2. Configuration APIs Collection

Both collections share the same authentication flow (OAuth 2.0), and you can use the same environment for both.

📘

Postman Definitions

  • A collection is a set of API endpoints or requests, along with each endpoint's authorization type, parameters, headers, request bodies, tests, and settings grouped together.
  • A environment is a set of one or more variables that you can reference when sending requests or writing test script in Postman.

Prerequisites

Forking the Collections and Environment

Both collections and the environment are hosted inside the official New HPE Aruba Networking Central Postman Workspace. Follow these steps:

  1. Open the workspace above in Postman.
  2. Locate the following assets pinned in the workspace sidebar:
    1. MRT APIs (Collection)
    2. Configuration APIs (Collection)
    3. New HPE Aruba Networking Central ENV (Environment)
  3. Click the Fork button on each item to fork them into your own Postman workspace.

    📘

    Note

    Forking creates a personal copy of the official Postman collections and environment in your own workspace.
    This lets you safely test APIs, change variables, and make changes without affecting the shared workspace.

Steps to fork a collection & environment to your own workspace

Steps in action: forking the collection and environment into your own Postman workspace.

Setting Up the Environment

  1. In your workspace, go to the Environments tab in Postman.

  2. Select the New HPE Aruba Networking Central ENV & click the checkmark icon to set it as the active environment.

  3. Configure the following variables

VariablesDescriptions
baseUrlThis URL will be based on the geographical cluster in which your Central account is provisioned. You can find the base URLs for all the new Central clusters in this table.
client_id and client_secretEnter your API client credentials for new Central. These are required for OAuth 2.0 authentication to securely make API requests to New HPE Aruba Networking Central API Gateway. You can find steps to generate API client credentials here .

Authentication Setup

Central uses OAuth 2.0 for secure API authentication, and the Postman collections leverages this to simplify token management. Once the above mentioned environment variables are configured, you can generate and store access tokens automatically.

  1. After configuring the New HPE Aruba Networking Central ENV variables, ensure the environment is active.
  2. In either collection, open the Auth section and click “Get New Access Token.”
  3. Postman will use OAuth 2.0 to request a new token from Central and automatically save the token.
  4. Once the request succeeds, your token is ready for use. You can immediately make API calls to Central from the Postman collection.
Steps in action: setting up the environment and completing authentication in Postman

Steps in action: setting up the environment and completing authentication in Postman

Updated 10 days ago

What’s Next

Once authentication is complete, you can: