Security & Backup

NordLayer

Manage NordLayer client organizations from Dex - roster, service plans, and license counts through the MSP Partner API.

Dex connects to the NordLayer MSP Partner API (the REST surface behind the Service Management Portal) to manage NordLayer client organizations as billing and licensing entities - list the customer roster, read an organization's details, create new client organizations, and update names, service plans, or license counts. The partner API manages organization lifecycle only; members, teams, gateways, servers, and device settings live in each organization's own Control Panel and are out of scope. Available as an MSP global app: one shared partner API key covers the whole partner account, and each Dex tenant is confined to its own NordLayer Organization via organization_id.

Start with $100 free →See Dex Live

What Dex does with NordLayer

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

List the MSP's NordLayer client organization roster (master connection only)
Read an organization's details: name, status, service plan, and member/server license counts
Create a new client organization with type, service plan, and license counts (master connection only) - with approval
Rename an organization and adjust member/server license counts - with approval
Change service plans (upgrades only - downgrades go through a NordLayer account manager) - with approval
Deploy as an MSP global app - one shared partner API key, each customer confined to its NordLayer Organization via organization_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>List all our NordLayer client organizations and their service plans
>What service plan and license counts does the Contoso organization have?
>Create a Trial organization for Northwind on the Core plan
>Upgrade the Acme organization from Lite to Premium
>Add 10 more member licenses to the Fabrikam organization

Policy actions

Every action Dex can take on NordLayer is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`nordlayer_list_organizations`	List the MSP's NordLayer client organizations (master connection only)	—
`nordlayer_read_organization`	Read a NordLayer organization's details: name, status, service plan, member/server license counts	—
`nordlayer_create_organization`	Create a new NordLayer client organization (master connection only) - billing-impacting: a Standard organization starts consuming licenses immediately	approval
`nordlayer_update_organization`	Update a NordLayer organization: rename, change service plan (upgrades only), adjust member/server license counts - billing-impacting	approval

How to configure NordLayer

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the NordLayer Service Management Portal (partner.nordlayer.com), go to Integrations > Custom > Create API key.
2
Name the key, set an expiration date, and copy the value - it is shown only once at creation.
3
In Dex, enable the NordLayer integration and paste the partner API key on the MSP-master connection (leave organization_id blank).
4
Dex verifies the key with a live call, then uses GET /v1/organizations to map each tenant to its numeric Organization ID.
5
For each customer tenant, set organization_id on that tenant's connection to confine every call to that organization.

Credentials required

api_key: NordLayer partner API key from SMP > Integrations > Custom > Create API key (shown once; has an expiration date)
organization_id: This tenant's numeric NordLayer Organization ID - leave blank on the MSP-master connection, set it on each tenant connection for per-customer isolation

Requirements

•A NordLayer MSP partner account with access to the Service Management Portal (partner.nordlayer.com)
•A partner API key created under Integrations > Custom (keys expire - schedule rotation before the expiration date)
•Organization lifecycle only - members, teams, gateways, and servers live in each organization's Control Panel, which has no public REST API
•For MSPs, the integration deploys as a global app: one shared key, each tenant scoped to its Organization via organization_id