Connect Dicker Data

Dicker Data is an IT distributor serving Australia and New Zealand. Partners buy hardware, software and cloud subscriptions through it, run Microsoft CSP customers on it, and bill annuities from it. StackJack talks to Dicker Data through its B2B partner API, which is the same interface that sits behind the partner portal you already use.

Connecting Dicker Data to StackJack gives your AI assistant a family of dicker_ MCP tools — MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

• Price and source — live price and stock for a list of part numbers, product detail, your partner program status, and an order template you can build a real order from
• Track orders — order details and lists, serial numbers for what shipped, and consignment status for what is still in transit
• Reconcile billing — invoices and their line detail, Microsoft CSP invoice reporting, and your annuity schedule with its order items
• Report on subscriptions — subscription detail, usage, renewal detail, the actions a given subscription will accept, and whether it is eligible to transition to another plan
• Work Microsoft CSP — customer entitlements, tenant lookup by domain, available add-ons, CSP part numbers, agreement acceptance detail, and the status of software delivery keys
• Follow Autodesk renewals — license lookups by serial number, term-switch availability, and your renewal opportunities
• Buy and provision (on Pro plans) — place hardware and subscription orders, create purchase orders, confirm annuity billing, create and change subscriptions, provision and edit Microsoft CSP tenants, sign customer agreements, issue software delivery keys, and transact Autodesk renewals

How StackJack authenticates to Dicker Data

Dicker Data gives you two values: an access token and your account code. You paste both into StackJack. There is no client ID, no second secret to rotate, and nothing to renew on a schedule.

Behind the scenes Dicker Data does not accept the access token directly on each request: it exchanges it for a short-lived key first. StackJack handles that exchange for you, keeps the key fresh, and gets a new one automatically when it expires. You never see it.

Pick your country and environment

This is the one decision worth making carefully, because Dicker Data runs Australia and New Zealand as separate services — separate systems, separate data, and usually separate credentials. Alongside each one there is a full sandbox.

So the connector asks you for two more things beyond the token and account code:

• Country — Australia or New Zealand. Choose the one your account belongs to. An Australian credential will not work against the New Zealand service.
• Environment — Production or Sandbox. Choose Sandbox if you entered sandbox credentials.

StackJack stores these as your choices rather than as a web address, so the connection cannot drift onto the wrong country later.

Steps

1. Ask Dicker Data to switch on the Access Token Service for your account. Email integration.support@dickerdata.com.au. It is not on by default, and nothing else works until it is.
2. Ask for sandbox credentials at the same time. Dicker Data runs a full sandbox with the same features as the live service, and it is the only safe place to try a write. See the warning below for why this matters more here than on most connectors.
3. Copy your access token and account code from the partner portal, under Account, then Integration, then API Tokens. Treat the token as a password: anyone holding it can price, order and manage subscriptions on your account.
4. Enter both in StackJack. Open Connectors, choose Dicker Data, paste the two values, then pick your country and environment.
5. Run a Test Connection to confirm StackJack can reach Dicker Data. StackJack checks both values together, so a failure means one of them, the country, or the environment is wrong.

What to know before your AI uses this connector

Every write spends money, and there is no draft state

This is the most important thing about the Dicker Data connector, and it makes it unlike any other connector in StackJack: there is no harmless write here. Every write tool is marked destructive, without exception, because each one either spends real money, signs or attests a legal agreement on a customer's behalf, provisions or re-binds a real Microsoft tenant, ends live billable service, or issues a software key with resale value.

• Placing an order ships physical goods to the delivery address in the request. There is no draft state and no undo.
• Creating or changing a subscription changes live billing on a real customer, immediately.
• Provisioning a Microsoft tenant creates a real tenant, and associating one re-binds an existing customer to your account.
• Signing a customer agreement is a legal signature made on the customer's behalf.
• Issuing a software delivery key mints something with resale value, and returning one voids it.

Every one of these requires the Pro tier and is marked destructive. Whether your AI application asks you to confirm before running one depends on that application's own settings — see Destructive tools and confirmation. Review that setting, and use the sandbox the first time you try any of them.

Three tools deserve a closer look before you let an assistant near them:

• The Autodesk subscription order is the least safe tool in the connector. Dicker Data publishes no description of what its request should contain and returns no content at all, so nothing in the reply confirms what was ordered. Where the job can be done with the standard subscription order instead, use that.
• The manage-subscription tool takes a free-form action, so suspend, cancel and quantity change all run through one tool. Ask your assistant to read the accepted actions for that subscription first and use only a value that came back.
• Editing a Microsoft tenant replaces the whole record. There is no partial update, so a field left blank will most likely clear the stored value. Supply the complete record.

Reads change nothing, even though many of them look like writes

Most of this API works by sending a request body rather than by reading a web address, so a large number of read-only tools technically send data to Dicker Data. They still create nothing and change nothing. Live pricing, tenant lookup, CSP reporting and opportunity reads all fall into this group, and StackJack classifies them by what they actually do rather than by how they travel. They are Free-tier reads and are not marked destructive. They do return your pricing and your customers' commercial detail, so grant them deliberately.

Each area is enabled separately on your account

Autodesk, electronic software delivery, annuity billing and Microsoft CSP are each switched on separately per account. If one area is refused while everything else works, the cause is almost always enrollment rather than a fault. Ask Dicker Data to enable the one you need.

Large reads are bounded by a date range, not by pages

This API has no paging. Every large read takes a date window instead, and both ends are usually required. Keep the window tight: a wide one returns everything in it at once. Dicker Data does not document a date format anywhere, so each tool asks for the standard year-month-day form and passes the dates on exactly as given. If a date read comes back empty or refused, the format is the first thing to check.

Prices and quantities come back as text

Dicker Data returns prices, stock levels and dimensions as text rather than as numbers, and it expects them the same way on the way in. StackJack passes them through exactly as they are, so an assistant reading a price gets the vendor's own value with no rounding of ours in between.

Plans and limits

Read tools are available on the Free tier. Everything that orders, bills, provisions, signs or issues a key is Pro. Business reaches the same tools as Pro and differs by monthly call quota.

See the generated Dicker Data tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Dicker Data publishes no rate limit, so StackJack paces requests conservatively and backs off on its own if it is throttled, which usually makes a large report slower rather than failed. Pacing smooths a burst; it does not guarantee that every call arrives. Retries are bounded, so a wide enough read can still come back throttled or time out. Narrow the read, honour any retry delay the vendor sends, and check whether a write landed before repeating it — see Retrying a failed or timed-out write.

Several customers

Every country you trade in has its own Dicker Data account. Add one connection per country from the connector's card, name it after the country, and your AI names it on each call. Omit the name and the call runs against your default connection. Pin an endpoint to one connection when an AI should never reach past a single customer. See Several connections of one connector.

Troubleshooting

"Dicker Data refused the access token" — the token, the account code, or the pairing between them is wrong. Check that the token has not been regenerated in the partner portal, and check that the country and environment match the credentials you entered. An Australian token sent to the New Zealand service fails exactly this way, and so does a live token sent to the sandbox.

A request succeeds but reports a problem — this API can answer successfully at the transport level while telling you in the reply that it refused the request. StackJack treats that as a failure and shows you Dicker Data's own message, so an assistant never reports an order as placed when it was not. The message is usually specific: an unentitled account, an invalid part number, or a rejected order line.

One family of tools is refused while everything else works — that is enrollment, not a fault. Autodesk, software delivery, annuity billing and Microsoft CSP are each enabled separately. Ask Dicker Data to switch on the one you need rather than re-issuing your access token.

A read returns far more than you expected — narrow the date window. There is no page size to reduce, so the window is the only control over how much comes back.

An Autodesk license lookup asks for a token — that is an Autodesk token you supply, and it is a different thing from your Dicker Data access token. StackJack attaches the Dicker Data credential on its own and never sends it to Autodesk.

Dicker Data tools

dicker_ · 57 tools · Free 34 · Pro 23

Catalog & Pricing

Orders & Fulfillment

Invoices & Annuity Billing

Subscriptions

Microsoft CSP

Autodesk & Opportunities