Connect Pax8

Pax8 is a cloud distribution marketplace — partner billing, subscriptions, quoting, and vendor provisioning. Connecting Pax8 to StackJack lets your AI assistant work with your Pax8 partner data through MCP tools (MCP is the Model Context Protocol, the open standard AI assistants use to call external tools).

Once connected, your AI can work with companies and contacts, products and pricing, subscriptions, orders and invoices, usage summaries, and quotes through tools with the pax8_ prefix (for example pax8_list_subscriptions). See the generated Pax8 tool reference for the current inventory, input schemas, plan tiers, and safety notes.

Before you begin

You'll need:

• A StackJack role that can manage connectors: Owner, co-owner, or Administrator.
• Access to the Pax8 developer portal at devx.pax8.com for your organization.

The same steps below are also shown inside the portal — open Connectors, find the Pax8 card, and click How To Connect.

Step 1 — Create an API Application in Pax8

1. Go to the Pax8 developer portal (devx.pax8.com) and create a new API Application for your organization.
2. Pax8 issues a Client ID and Client Secret for the application. The secret is shown only once — copy it immediately.
3. Check which API surfaces your application can reach. Typical MSP partners get the standard partner audience (https://api.pax8.com), covering companies, subscriptions, quoting, and billing. The vendor provisioning (api://provisioning) and vendor usage (api://usage) audiences require separate Pax8 marketplace-vendor onboarding — tools in those areas will not work without it.

See Pax8's authentication documentation for the current details.

Step 2 — Connect in StackJack

1. In the StackJack portal, open Connectors from the sidebar.
2. Find the Pax8 card and click Configure (or How To Connect first for the in-portal walkthrough).
3. Fill in the form:

There is no URL field — the Pax8 API lives at a single global endpoint (https://api.pax8.com), shown as fixed text in the dialog.

4. Click Save.

What happens when you save

• Your credentials are stored encrypted in Azure Key Vault — never in StackJack's database, and never shown back to you.
• A Free plan for Pax8 is activated automatically, so your AI can start calling Pax8 tools right away.
• StackJack immediately runs a live validation call against Pax8. If validation fails, your credentials are still saved — fix the underlying issue and click Re-test on the card.
• Behind the scenes, StackJack exchanges your Client ID and Secret for Pax8 access tokens using the OAuth 2.0 client_credentials grant, requesting the right audience for each endpoint family. Pax8 tokens last a fixed 24 hours; StackJack caches and renews them per audience automatically, so you never manage tokens yourself.

Access and safety

The Pax8 API token represents a Pax8 user, so what your AI can see and change is governed by that user's role and account permissions. If the user behind the API application lacks permission on an account, those endpoints return empty or filtered results rather than errors — a common cause of "the data looks incomplete".

Treat the Client Secret as a high-impact credential: the partner surface includes write operations such as ordering, subscription changes, and company creation. Scope the Pax8 user behind the application accordingly, and never send the secret in a ticket, chat, or email.

The Pax8 tool family spans these areas:

To see exactly which tools touch which areas — and to scope an AI client to a smaller tool set — open Permissions in the portal and select Pax8.

StackJack's per-client tool assignments limit what an AI client may request through StackJack, but they do not make the Pax8 credential itself less privileged — scope the Pax8 user as well as the tool list.

Partner data and the Pax8 marketplace-vendor APIs are separate contracts. Vendor provisioning and vendor usage require Pax8 marketplace-vendor onboarding and the api://provisioning or api://usage audience; ordinary partner access does not grant those surfaces.

Note: the four provisioner-webhook tools (pax8_vendor_list_provisioner_webhooks, pax8_vendor_get_provisioner_webhook, pax8_vendor_get_latest_provisioner_webhook, and pax8_vendor_create_provisioner_webhook) configure the endpoints Pax8 delivers provision events to. They belong to the Vendor Provisioning group and need the same api://provisioning audience as the rest of it.

Plans, tools, and usage limits

• See the generated Pax8 tool reference for the current tool inventory, plan tier, and destructive-operation labels. Use the Portal for current pricing and monthly allowance.
• Pax8's API allows 1,000 successful calls per minute per client; exceeding it returns HTTP 429 until the window resets. StackJack paces its own Pax8 requests to keep your tenant under that limit.
• Pax8 list endpoints use zero-based page numbers; continue through totalPages - 1. Individual StackJack tools expose their supported paging inputs in the generated reference.

Troubleshooting

Disconnecting

On the Pax8 card, click Disconnect and confirm. This deletes StackJack's stored credential and stops all Pax8 tool calls. It does not revoke the credential in Pax8; revoke that separately if the connection is being retired.

⚠ Disconnecting does not cancel a paid Pax8 plan — billing continues until you cancel it separately. The plan controls only appear while the connector is connected, so end the plan before disconnecting. On a paid connector that button reads Manage on Billing and opens this connector's removal dialog on the Billing page; a legacy website subscription still reads Cancel Plan. If you've already disconnected, save your credentials again to bring the plan controls back, then end the plan.

Pax8 tools

pax8_ · 86 tools · Free 86

Companies

Contacts

Invoices

Orders

Products

Subscriptions

Usage Summaries

Quotes

Quote Line Items

Quote Sections

Quote Attachments

Quote Access List

Quote Preferences

Library Attachments

Vendor Provisioning

Vendor Usage