How can Postman be used with Ruckus One (R1) Cloud APIs to handle arrays of strings in GET and POST API requests?

This includes:

• Retrieving arrays of strings using GET commands
• Sending arrays of strings

• Customer is unsure how to retrieve an array of strings from R1 APIs using Postman
• Confusion between using GET versus POST methods for APIs that return string?based data
• Difficulty formatting request bodies when arrays of strings are required

1. Using Arrays of Strings in POST Requests

For APIs that require a request body (such as POST or PUT), the array of strings must be added in the Body section of Postman.

Refer to the official Ruckus One API documentation for supported request formats:
https://docs.ruckus.cloud/api/

Note: PUT commands always require a request body, whereas GET commands do not.

2. Using GET Requests to Retrieve Arrays of Strings

Many R1 APIs return arrays of strings directly in their response payload. These can be accessed using GET requests without specifying a body.

Region?specific Client API Endpoints

• US Region:

  https://api.ruckus.cloud/clients
  

• EU Region:

  https://api.eu.ruckus.cloud/clients
  

• Asia Region:

  https://api.asia.ruckus.cloud/clients
  

3. Retrieving AP Information (Array of Strings)

Use the following GET calls to retrieve AP?related data:

• Get all APs in all venues:

  GET https://api.asia.ruckus.cloud/venues/aps
  

• Get AP details using venue ID and serial number:

  GET https://api.asia.ruckus.cloud/venues/{venueId}/aps/{serialNumber}
  

4. Retrieving Venue ID

To obtain a venue ID required for venue?specific API queries:

GET https://api.<region>.ruckus.cloud/api/tenant/{tenantId}/venue

When using Postman with Ruckus One APIs:

• Use GET requests to retrieve arrays of strings (for example, client or AP information)
• Use POST or PUT requests only when the API explicitly requires a request body
• No POST command is required when the API endpoint already returns data through GET

Example JSON Output (Array of Strings)

The following example shows a typical response for a client record retrieved via a GET request:

{
"mac": "00:00:00:00:00:00",
"apMac": "00:00:00:00:00:00",
"osType": "Android",
"venueId": "xxxxxxxxxxxxxxx",
"connectedSince": "2025-07-08T05:03:04Z",
"apSerialNumber": "xxxxxxxxx",
"networkId": "xxxxxxxxxxxxxxx",
"ip": "0.0.0.0",
"username": "xyz",
"hostname": "username",
"ssid": "SSIDname",
"vlan": vlanID
},