Skip to main content
This guide walks you through connecting your Addigy instance to MSPortal.ai. Addigy is a cloud-based Apple device management platform, and this integration syncs your policies and macOS/iOS devices into MSPortal. You choose data, match policies to companies and import devices on the Addigy connection page.

Overview

The Addigy integration syncs your Apple device fleet into MSPortal, allowing you to:
  • Import and manage macOS devices from Addigy
  • Map Addigy policies to your MSPortal companies
  • Keep device inventory synchronized automatically
  • View extended device details including hardware, security, battery, and MDM status
  • Track devices in reports and compliance workflows

Prerequisites

Before you begin, ensure you have:
  • Active Addigy account with administrative access
  • MSPortal.ai account with integration management permissions
  • Companies already set up in MSPortal (from your PSA integration or manually created)
The Addigy integration maps policies to existing companies in MSPortal. Import your companies from your PSA integration first, or create them manually before setting up Addigy.

Part 1: Generate an API Token in Addigy

Before connecting to MSPortal, you need to create an API token in Addigy.
1

Log into Addigy

Access your Addigy portal at app.addigy.com.
2

Navigate to API Settings

Go to Account > Integrations > API & Webhooks > V2.
Use a V2 API token. The older V1 Client ID and Client Secret pair does not work with MSPortal.
3

Create a New API Token

Click New API Token and give it a descriptive name (e.g., “MSPortal Integration”).
A read-only API token is sufficient for MSPortal to sync your device and policy data. This follows the principle of least privilege.
4

Copy Your Token

Copy the generated API token immediately.
Copy the API token right after creation. It may not be retrievable once you close the dialog. Store it securely for use in MSPortal.

Required Information

Before proceeding to MSPortal, ensure you have:

Part 2: Connect Addigy in MSPortal

The Addigy connection page has five setup tasks: Connect, Choose data, Import or match policies, Import devices and Review. Select a task in the Setup guide to return to it at any time.

Open the connection

1

Navigate to Integrations

In MSPortal, go to Settings > Integrations.
2

Start Setup

Find Addigy and select Connect. To manage an established setup, open the existing Addigy connection instead.

Connect

Enter your Addigy API token to establish the connection.
1

Enter API Token

Paste your Addigy V2 API token into the API Token field.
Your token is stored securely using encrypted vault storage. It is never exposed in logs or API responses.
2

Test the connection

Select Test connection to verify your token. Connection verified appears when the test passes.If the connection fails:
  • Verify your API token is copied correctly without extra spaces
  • Ensure the token has not been revoked or expired
  • Confirm your Addigy account has API access enabled
3

Save and continue

Once the test passes, select Save and continue. This saves the connection and starts discovering your policies. A successful test alone does not save the connection.

Choose data

Addigy has no optional datasets, so MSPortal syncs all supported Addigy data. Open Choose data to start the initial sync when it is offered and follow its progress. The first sync runs in the background and may take 10 minutes or more depending on device count.

Import or match policies

Map your Addigy policies to MSPortal companies. Addigy uses policies as the primary organizational unit (similar to sites in other RMM tools). Saved matches decide which company receives each policy’s devices.
1

Load policies

Open Import or match policies. If no policies appear yet, select Sync policies and wait a few minutes for the background sync.
2

Review suggestions

Use Suggested to review proposed matches. Each suggestion shows its confidence. Select Accept on a row to save that match, or use Review N suggested matches to accept several at once. It opens Accept suggested matches, which lists every suggestion at 70% confidence or more with those at 90% or more already selected. Lower the Auto-select by confidence slider, as far as 70%, to select weaker suggestions too, untick any pair you want to check yourself, then select Apply N Matches.
3

Match the remaining policies

Use Import to find policies without a match. Select Choose company… to pick an existing MSPortal company, or select Import on the row to create a company from the policy and match it. Import companies imports several policies at once; existing companies with the same name are matched instead of duplicated. Check for an existing company first to avoid duplicates.
4

Check saved matches

Use Matched to review saved links. To unlink a policy, select Change and choose Remove match; it takes effect immediately. Use Ignore for policies you never want to map.
Each match saves as soon as you apply it; wait for the confirmation before you leave. Review sync results separately from the matching result.
Match at least one policy before you import devices. Devices from unmatched policies show Match company first and are not imported.

Import devices

Open Import devices to map device types and import devices on the connection page. Every change saves immediately. For more detail, see Import Devices.
1

Match device types

Under Match device types, choose the MSPortal device type each Addigy type becomes. Select Match all suggested to accept the suggestions, Match the rest with AI for the remaining types, or Choose device type… on a row. Use Ignore on types you never want to import.
2

Turn on Auto-import (Optional)

Turn on Auto-import for device types you want imported automatically. New devices of those types are imported during each sync cycle. A type needs a device type before it can be auto-imported.
3

Import staged devices

Staged devices lists the devices Addigy sent that are waiting to be imported. Select devices and choose Import n selected, or choose Import all matched to import every device whose type is matched. To hide devices you never want to import, select them and choose Ignore n selected.
4

Check the result

Check the import result and the new records in the Devices module.
The staged device list shows each device’s name, type, company, model, operating system and import status. Addigy devices are always made by Apple.

Review

Open Review and select Finish setup once the required tasks are complete. Finishing setup does not mean every background sync or device import has completed.

What Gets Synced

Extended Device Data

Devices imported from Addigy include rich extended data visible in the Device Detail view. Click any device in the Devices module to see:
  • Hardware - Processor, RAM, total and free disk space with usage percentage
  • Security - FileVault encryption, Firewall, Gatekeeper, System Integrity Protection (SIP), MDM enrollment, supervised status
  • Network - Hostname, LAN IP, WAN IP, Wi-Fi and Ethernet MAC addresses
  • Battery - Battery percentage, charging status, and cycle count
  • User - Current logged-in user and email
  • System - OS version, agent version, last seen time
Importing an Addigy device into MSPortal does not enroll it in Addigy MDM. Enrollment and policy administration stay in Addigy.

Sync Schedule

Addigy data syncs automatically on the following schedule: You can request a sync at any time with Run sync on the Addigy connection page. A scheduled time does not guarantee a successful run, so check Sync activity when data looks old.

Managing Your Integration

After setup, manage the integration from its connection page:

Replacing or Retesting the Token

1

Open the connection

Go to Settings > Integrations and open the Addigy connection.
2

Open Connect

Select Connect in the Setup guide. The stored token shows masked.
3

Retest or replace

To check the stored token, select Test connection without changing the field. To replace it, paste a new V2 token, select Test connection, then select Save changes.
Retesting alone does not save a new token. Do not disconnect a working connection just to diagnose a failed test, because disconnecting removes its matches and synced data.

Troubleshooting

Causes:
  • Incorrect API token
  • Token has been revoked or expired
  • A V1 credential was used instead of a V2 token
  • Addigy account does not have API access enabled
Solutions:
  1. Verify your API token is copied exactly, without extra spaces
  2. Generate a new V2 API token in Addigy (Account > Integrations > API & Webhooks > V2)
  3. Confirm your Addigy account has API access permissions
Causes:
  • Initial sync still in progress
  • API token lacks read permissions
Solutions:
  1. Wait a few minutes for the background sync to complete
  2. Select Sync policies, or use Run sync on the connection page
  3. Verify your API token has the necessary read permissions in Addigy
  4. Avoid creating extra connections to work around an empty list
Check the result of the last matching action, then reopen Import or match policies and look in Matched to confirm the saved state. Removing a saved match takes effect immediately.
Causes:
  • No policies have been matched to companies
  • Device sync still in progress
  • Policies do not have any enrolled devices
Solutions:
  1. Match at least one policy to a company in Import or match policies
  2. Wait for the device sync to complete (can take several minutes initially)
  3. Use Run sync to request a fresh sync
Causes:
  • Device type not mapped
  • Policy match was removed
  • Device type or device is ignored
Solutions:
  1. Ensure every device type you want has a device type under Match device types
  2. Verify the policy is still matched to a company
  3. Check for error messages in the import results
Causes:
  • Auto-import not turned on for the device type
  • Device type not mapped
  • Policy not matched to a company
Solutions:
  1. Turn on Auto-import for the device type
  2. Ensure the device type is mapped to an MSPortal device type
  3. Verify the device’s policy is matched to a company
Causes:
  • Device was recently imported and extended data has not synced yet
  • Device is offline and Addigy cannot collect current facts
Solutions:
  1. Wait for the next sync cycle to populate extended data
  2. Use Run sync to request a manual refresh
  3. Verify the device is online in your Addigy portal
Check the last successful sync in Sync activity, whether the connection is paused, and any connection errors.

Frequently asked questions

No. For a new connection, complete the successful test and then choose Save and continue. On an existing connection, retesting is separate from Save changes.
No. Device discovery, saved matches and device imports have separate results. Check Import devices and the resulting inventory.

Best Practices

Map Policies First

Always match your Addigy policies to companies before trying to import devices. Devices from unmatched policies cannot be imported.

Accept Suggested Matches

Start with Review N suggested matches for policies, then review the rest yourself. It saves significant time.

Turn On Auto-import

For device types you always want imported (like MacBooks and iMacs), turn on Auto-import to reduce manual work.

Ignore Unwanted Types

Use Ignore to hide device types you do not manage. This keeps your import list clean.

Security and Privacy

  • Credential Storage: Your Addigy API token is encrypted using vault storage and never exposed in logs or responses
  • Data Isolation: All synced data is tenant-isolated and only visible to your organization
  • Read-Only Access: MSPortal only requires read access to Addigy data; it never modifies your Addigy configuration
  • Rate Limiting: MSPortal uses conservative API rate limits to avoid triggering Addigy’s rate limit protections

Need Help?

For assistance with the Addigy integration, contact support@msportal.ai.