Bring Aditum Connect® controls into the systems you already run.

The API is for system integrators and service operators who want tenant account controls, location visibility, and plan management to live inside the workflows they already use.

What Teams Usually Need

The practical integration layer

  • Pull live client, location, and tenant records
  • Expose supported account actions inside your own portal
  • Connect plan changes to existing customer workflows
  • Reduce support handoffs between tools

Where It Fits

Use it where the work already happens

The strongest integrations keep operators and tenants inside familiar systems. This page should help technical buyers understand what data is available, what the screens look like, and where the deeper live reference sits.

Reference Screens

Review each API operation in context.

 

1

List available clients

Start by retrieving the client records available to the authenticated partner or operator account.

View client list screen

List all available clients

List all available clients.

2

Retrieve location details

Pull location-level details and performance statistics when your system needs a deeper view of a specific property.

View location detail screen

Retrieve location details and performance statistics

Retrieve location details and performance statistics.

3

List locations

Use the location list to identify the properties that can be queried, managed, or exposed inside an external workflow.

View location list screen

List all locations

List all locations.

4

List available plans

Retrieve bandwidth plans before presenting tenant plan options or account-change controls.

View plan list screen

List available bandwidth plans for a location

List available bandwidth plans for a location.

5

List tenant accounts

Pull tenant account records for operational review, support workflows, or partner-facing account management screens.

View tenant list screen

List tenant accounts

List tenant accounts, including partner-filtered views.

6

Update tenant parameters

Use supported update actions when an external workflow needs to change tenant account settings.

View tenant update screen

Update supported tenant account parameters

Update supported tenant account parameters.

7

Look up a tenant by username

Retrieve a specific tenant account when a workflow starts from a username instead of a location-wide list.

View username lookup screen

Retrieve account details for a specified username

Retrieve account details for a specified username.

8

Review tenant status by location

Retrieve current tenant status and account details when the workflow needs a building-level view.

View location status screen

Retrieve current status and details for all tenants at a location

Retrieve current status and details for all tenants at a location.

Typical Workflows

Most integrations follow a small number of patterns.

You do not need a sprawling integration to get value. The strongest implementations usually start with a tight operational use case and expand from there.

1

Pull the records you need

List clients, locations, tenant accounts, or available bandwidth plans so your own system starts from live Aditum Connect® data.

2

Expose the right controls

Present plan-change or account-management actions inside your existing portal, CRM, or support workflow instead of sending users somewhere else.

3

Keep operations aligned

Use the same integration to support tenant experience, service operations, and account workflows across the property.

Common Operations

What teams usually call first

  • List all available clients
  • Retrieve location details and performance statistics
  • List available bandwidth plans for a location
  • List tenant accounts, optionally filtered by client
  • Retrieve account details for a specified username
  • Update supported parameters for a tenant account
  • Retrieve current tenant status for a location

Live Reference

Keep the detailed documentation nearby

The expandable reference cards help teams scan the API quickly. The embedded reference keeps the full endpoint material available on the same page instead of sending them into a disconnected experience.

Note: the embedded reference is still here for deeper endpoint review after the summary cards.

Explore Next

Move from API fit into the rest of the platform.

If this page answered the integration question, these are the next pages that explain deployment, wireless architecture, and partner fit.