[Dicker Data] Build an order template from a list of part numbers. Despite being a POST this creates NO order and spends nothing — it returns the line structure Dicker Data would expect, which is the safe way to prepare an order body before handing it to dicker_create_order for a human to approve. Pass up to 100 part numbers; StackJack drops anything beyond that.

[Dicker Data] Get the partner-program tier and details Dicker Data holds for a reseller account. Leave the account code blank to use the account the stored credential belongs to. Useful for confirming which programs an account is enrolled in before calling a family that is separately entitled, such as Autodesk, electronic software delivery or annuity billing.

[Dicker Data] Get live reseller price and stock on hand for a list of Dicker Data part numbers. This is the primary catalog read and the one to reach for when quoting: it returns brand, part number, alternate part number, description, unit price, stock on hand, recommended retail price excluding tax, billing frequency and physical dimensions. Every numeric value comes back as a STRING, which is how Dicker Data types them — parse with an invariant culture rather than assuming a number. Pass up to 100 part numbers per call; StackJack drops anything beyond that because this API has no paging to fall back on. A part number is the vendor SKU, for example 8D8K2AA. To turn a Microsoft CSP SKU into a Dicker Data code first, use dicker_get_csp_stockcode.

[Dicker Data] Place a hardware order with Dicker Data. THIS SPENDS REAL MONEY AND SHIPS PHYSICAL GOODS to the delivery address in the payload — there is no draft state and no undo. Build the body with dicker_get_order_template first and have a person confirm it. The payload is the OrderIn block as a JSON object with three parts. Header: OrderNumber, Notes, BranchAccountCode, CurrencyCode, QuoteNumber. Delivery: DeliveryContact (FirstName, LastName, Phone, Fax, Email, Mobile), Attention, DeliveryAddress (CompanyName, Address01, Address02, Address03, Suburb, State, Postcode, Country), RequestedShippingDate, ShippingInstructions, PartShipped, ShippingMethod. Set ShippingMethod to DropShip to ship straight to the end customer. Items: an array, each with Product (Brand, PartNumber, Description, UnitPrice, SubscriptionType, Quantity, UseSystemPrice, SerialNumbers, LineNumber, UnitOfMeasure), optional EnduserFields, and Notes. Every value in this payload is a string, including quantities and prices.

[Dicker Data] Create a put-away purchase order. THIS CREATES A REAL COMMERCIAL DOCUMENT against the account and cannot be undone from this API. The payload is the Items array as JSON; each element takes WarehouseCode, Vendor, VendorReference, StockCode, StockDescription, Quantity, UnitPrice, CurrencyCode, HoldProcessingCode and Location. Every value is a string, quantities and prices included.

[Dicker Data] Get freight tracking status for a consignment. The consignment number comes from the order detail returned by dicker_get_order_details once the order has shipped.

[Dicker Data] Get one order's detail. Identify it by Dicker Data order number, by reseller account code, or by the customer purchase-order reference that was sent with it. Supply at least one. To list several orders instead, use dicker_list_order_details; for the serial numbers actually shipped, use dicker_get_order_serials.

[Dicker Data] Get the serial numbers shipped against an order. Both the order number AND its suffix are required — the suffix identifies which shipment within the order, and an order that ships in parts has several. Get both from dicker_get_order_details.

[Dicker Data] List orders, filtered by reseller account code, order number, backorder number or customer purchase-order number. Dicker Data has no paging and no date filter on this operation, so narrow it with at least one identifier rather than asking for everything an account has ever ordered.

[Dicker Data] Confirm annuity orders. THIS COMMITS BILLING for every line confirmed and cannot be undone from this API. Read dicker_get_annuity_order_items first and have a person approve the list. The payload is the ConfirmAnnuityList array as JSON; each element takes AnnuityID, SalesOrderNumber, SalesOrderSuffix, SalesOrderLineSequence, StockCode, Quantity, CustomerReference and ConfirmFlag. Every value is a string.

[Dicker Data] Get the line items on one annuity order. Identify it by sales order number plus suffix, or by annuity id — both come from dicker_list_annuities. Read this before dicker_confirm_annuity_orders so a person can see exactly what is about to be committed to billing.

[Dicker Data] Get the Microsoft CSP invoice report for a date window. This is the read that reconciles CSP billing against a PSA without a human: it covers the subscription charges Dicker Data invoiced in the period. Both ends of the window are required. Dicker Data does not document a date format; send ISO-8601 (YYYY-MM-DD). CSP is separately entitled per account, so an account that is not enrolled will be refused — that is normal, not a broken credential.

[Dicker Data] Get the invoice lines for one sales order. The sales order number comes from dicker_list_invoices; the suffix identifies which shipment within that order was invoiced, so an order that shipped in parts has several. Set includeCustomerQualification to true to include the customer-qualification data Dicker Data holds against the lines.

[Dicker Data] List annuity (recurring) billing records of a given type over a billing-date window. Both ends of the window are required. Annuity billing is separately entitled per account, so an account not enrolled in it will be refused — that is normal. For the lines on one annuity order use dicker_get_annuity_order_items; to confirm annuity orders, which commits billing, see dicker_confirm_annuity_orders.

[Dicker Data] List reseller invoices raised in a date window. Both ends are required: this API has no paging, so an open range would return everything at once. Dicker Data does not document a date format for this parameter; send ISO-8601 (YYYY-MM-DD). For the lines on one invoice, follow up with dicker_get_invoice_details.

[Dicker Data] Create one or more billable subscriptions against a tenant. THIS SPENDS REAL MONEY on a recurring basis and cannot be undone from this API — cancelling afterwards is a separate, separately-billed action. The payload is the In array as JSON; each element takes StockCode, Quantity, ParentStockCode, SubscriptionDescription, TenantID, MPNID, Email, UserName, SubscriptionID, Action and SubscriptionType. Get the StockCode from dicker_get_csp_stockcode. Every value is a string, quantity included.

[Dicker Data] Look up a license by its serial number. For Autodesk licenses specifically, dicker_get_autodesk_license takes several serials at once and can include related assets.

[Dicker Data] List the actions Dicker Data will accept against a subscription right now. ALWAYS call this before dicker_manage_subscription, whose Action field is free-form: pass only a value this returned. Identify the subscription by tenant id, subscription id, order id, parent subscription, stock code, subscription reference or subscription type.

[Dicker Data] Get subscription detail. Identify the subscription by any of six keys: Microsoft tenant id, subscription reference, Dicker Data stock code, subscription id, subscription type or order id. Supply at least one; supplying more narrows the result. For a richer projection use dicker_get_subscription_details_extended, and for what may legally be done to it use dicker_get_subscription_actions.

[Dicker Data] Get the extended subscription-detail projection. Takes the same six identifiers as dicker_get_subscription_details and returns Dicker Data's richer view of the same subscription. Dicker Data does not document which extra fields the extended form adds, so compare the two on a real subscription rather than assuming.

[Dicker Data] Get metered consumption for a subscription over a usage period — the Azure-style usage lines behind a consumption bill. All four parameters are required; there is no paging, so the period is what bounds the response. Dicker Data does not document a date format for the period; send ISO-8601 (YYYY-MM-DD).

[Dicker Data] Act on a live subscription. THE ACTION FIELD IS FREE-FORM, so this one tool covers suspend, cancel and quantity change — its blast radius is whatever Dicker Data accepts. CALL dicker_get_subscription_actions FIRST and pass only an Action value that returned; anything else is a guess against a customer's live service. The payload is the In array as JSON; each element takes StockCode, Quantity, ParentStockCode, SubscriptionDescription, TenantID, MPNID, Email, UserName, SubscriptionID, Action and SubscriptionType. Every value is a string.

[Dicker Data] Place a subscription order with full end-customer, ship-to and reseller blocks. THIS SPENDS REAL MONEY and bills a named end customer. The payload is the In block as a JSON object: SubscriptionType, Action, EndCustomer (Account with CSN, Name, AltName, AddressLine1 to 3, City, Postcode, State, CountryCode; ContractManager with FirstName, LastName, Email, CountryCode, Language), ShipTo and Reseller (each Account plus Contact in the same shapes), ResellerPONumber, OpportunityNumber, ContractNumber, ContractStartDate, ContractEndDate, ContractTerm, SwitchFromContractNumber, SwitchToContractNumber, and LineItems (each PartNumber, PartDescription, UnitPrice, Quantity, PartnerSubscriptionId, SubscriptionReferenceNumber and optional PreviousSubscriptions). Quantity is a number here; the other values are strings.

[Dicker Data] Bind an existing Microsoft tenant to the reseller. THIS GRANTS A DELEGATED-ACCESS RELATIONSHIP over someone else's live Microsoft tenant and needs the customer's agreement before it is run, not after. The payload is the same In block as dicker_create_tenant; supply TenantID and AssociationEmail for an existing tenant.

[Dicker Data] Cancel a live Microsoft subscription. THIS ENDS SERVICE FOR A REAL CUSTOMER and cannot be undone from this API — reinstating means buying it again, and Microsoft's cancellation window may make a refund impossible. Confirm the subscription with dicker_get_subscription_details first and get a person's approval. One of subscriptionId or orderId is required; a call with only the tenant id is refused before it is sent.

[Dicker Data] Check whether an onmicrosoft domain prefix is available for a new CSP tenant. Despite being a POST this reserves nothing and changes nothing. Run it before dicker_create_tenant, which provisions a real Microsoft tenant and cannot be undone.

[Dicker Data] Create an attestation for the Microsoft Customer Agreement. THIS RECORDS A LEGAL ATTESTATION ON A CUSTOMER'S BEHALF, naming the person who agreed. It is the first half of the acceptance flow that dicker_submit_agreement_acceptance completes. The customer agreement data is a JSON object: PrimaryContact (FirstName, LastName, Phone, Fax, Email, Mobile) and CompanyName.

[Dicker Data] Provision one or more billable Microsoft subscriptions. THIS SPENDS REAL MONEY on a recurring basis. The payload is the In array as JSON; each element takes TenantId, StockCode, Quantity (a number), ParentSubscriptionId, SubscriptionDescription, MPNId, ChargeType, BillingFrequency, Email, UserName and CustomTermEndDate. Get the StockCode from dicker_get_csp_stockcode — a Microsoft SKU id will not work here.

[Dicker Data] Provision a real Microsoft CSP tenant. THIS CREATES A LIVE MICROSOFT TENANT under your CSP relationship and cannot be deleted from this API — a wrong domain prefix is permanent. Check the prefix with dicker_check_csp_domain first and have a person approve. The payload is the In block as a JSON object: DomainPrefix, FirstName, LastName, Phone, Email, CompanyName, Address01, Address02, Address03, Suburb, State, Postcode, Country, SubscriptionType, RelatedCSN, TenantID, AssociationEmail and TenantDescription.

[Dicker Data] Rewrite a live CSP tenant's name, contact and address. THIS IS A WHOLESALE REPLACE, NOT A MERGE: Dicker Data's model carries no partial-update signal, so a field you leave blank will most likely CLEAR the stored value. Read the current record with dicker_get_tenant and send it back complete with only the fields you mean to change edited. The payload is the In block as a JSON object: TenantId, TenantName, TenantDescription, FirstName, LastName, Email, Address1, Address2, Address3, Suburb, State, Postcode and Phone.

[Dicker Data] List the add-on SKUs that can be attached to an existing base subscription. Identify the base by subscription id, Dicker Data stock code or Microsoft offer id. Use this before dicker_create_subscription so an add-on is bought against a base that actually accepts it.

[Dicker Data] Get the Dicker Data stock code for a CSP subscription type. This is the join key between a Microsoft SKU and a Dicker Data line item: pricing, ordering and subscription creation all key off the stock code, not off the Microsoft SKU id, so this is usually the first call in a CSP purchasing flow.

[Dicker Data] Get the Microsoft entitlements Dicker Data holds for one CSP tenant. Resolve the tenant id from a domain first with dicker_get_tenant_id_by_domain if you only have the customer's domain name.

[Dicker Data] Check the status of an electronic software delivery token. The token here is the DELIVERY key issued by dicker_print_esd_token — a software key with resale value — and has nothing to do with the API credential. Electronic software delivery is separately entitled per account, so a refusal may simply mean the account is not enrolled.

[Dicker Data] Get the Microsoft Customer Agreement acceptance record Dicker Data holds for a tenant — who accepted it and when. Check this before signing anything: if a valid acceptance already exists, dicker_sign_mcua is not needed.

[Dicker Data] Get the Microsoft Customer Agreement template metadata, including the current template id that the signing and acceptance tools take. This is the one operation in the connector that needs no parameters at all.

[Dicker Data] Get Microsoft SKU detail for a tenant. Narrow with the Microsoft product id and SKU id when you have them. To buy the SKU through Dicker Data you also need its Dicker Data stock code — get that from dicker_get_csp_stockcode.

[Dicker Data] Get the renewal terms of a Microsoft subscription — what it will renew into and when. Read this before dicker_schedule_subscription_renewal or dicker_manage_subscription_auto_renew, both of which change future spend.

[Dicker Data] Get the CSP tenant record Dicker Data holds. Identify it by Microsoft tenant id, by onmicrosoft domain prefix, or by subscription type. Read this before dicker_edit_tenant_details, which replaces the record wholesale.

[Dicker Data] Resolve a Microsoft tenant id from a domain name. This is the usual entry point when you know a customer by their email domain and need the tenant GUID every other Microsoft tool takes.

[Dicker Data] Check whether a Microsoft subscription may transition to another SKU or term, and to which. Always read this before dicker_transition_subscription, which is irreversible and changes billing.

[Dicker Data] Turn auto-renew on or off for a Microsoft subscription, and optionally set a custom term end date. BOTH DIRECTIONS ARE CONSEQUENTIAL: turning it off means the customer's service lapses at term end, and turning it on commits future spend. Check the current state with dicker_get_subscription_renewal_detail first. Dicker Data types the flag as a STRING rather than a boolean.

[Dicker Data] Issue an electronic software delivery key. THIS MINTS A SOFTWARE KEY WITH REAL RESALE VALUE and is irreversible: the key is spent whether or not anyone uses it, and returning one is a separate action with its own rules. Have a person approve the SKU and the purchase order before running this.

[Dicker Data] Return and void an issued electronic software delivery token. THIS REVOKES A KEY: if the customer has already redeemed it, voiding it may break their installed software. Check dicker_get_esd_token_status first and have a person confirm the key is genuinely unused.

[Dicker Data] Schedule how a Microsoft subscription renews — billing cycle, term duration, quantity and custom term end date. THIS COMMITS FUTURE SPEND at the quantity and term given. Read dicker_get_subscription_renewal_detail first so a person can compare what it renews into today against what this would change it to.

[Dicker Data] Sign the Microsoft Customer Agreement for a tenant. THIS RECORDS A LEGAL SIGNATURE ON A CUSTOMER'S BEHALF and must never be run without that customer's explicit instruction. Check dicker_get_mcua_acceptance_details first — if an acceptance already exists, this is not needed. The agreement payload is a JSON object: UserId, PrimaryContact (FirstName, LastName, Phone, Fax, Email, Mobile), TemplateId (from dicker_get_mcua_metadata), DateAgreed, Type and AgreementLink.

[Dicker Data] Record a customer's acceptance of the Microsoft Customer Agreement against an attestation. THIS COMMITS A LEGAL ACCEPTANCE ON A CUSTOMER'S BEHALF. Run dicker_create_agreement_attestation first to get the attestation id, and get the template id from dicker_get_mcua_metadata. Never run either without the customer's explicit instruction.

[Dicker Data] Move a Microsoft subscription to another SKU or term. THIS IS IRREVERSIBLE AND CHANGES BILLING — a transition cannot be rolled back, only transitioned again. ALWAYS call dicker_get_transition_eligibility first and pass only a target it named; an ineligible transition can leave a customer between two states.

[Dicker Data] Issue or assign an Autodesk license. THIS COMMITS A LICENSE to the named account and is not reversible from this API. The payload is a JSON object: Token, SerialNumber (an array), PartnerCSN, AccountId, LoginId and CompanyCode. The Token here is an AUTODESK token you supply — it is unrelated to the Dicker Data API credential, which StackJack attaches on its own.

[Dicker Data] Place an Autodesk subscription order from a raw payload. THIS SPENDS REAL MONEY, and it is the least safe tool in the connector: Dicker Data publishes NO request model for it, accepts the body as an opaque payload, and answers with no content at all — so nothing in the response confirms what was ordered. Send exactly what Dicker Data's integration guide specifies for your account, have a person approve it, and check the result afterwards with dicker_get_order_details. Prefer dicker_place_subscription_order, whose contract is documented, wherever it can do the job.

[Dicker Data] Look up Autodesk licenses by serial number. Several serials can be sent at once as a comma-separated list, and related assets can be included. For a non-Autodesk license, dicker_get_license takes a single serial instead.

[Dicker Data] Get the Autodesk term-switch status for a location — whether Autodesk is currently accepting term changes there. Read it before dicker_update_autodesk_subscription, which changes a contract term and spends money.

[Dicker Data] Get one opportunity by partner CSN, contract number or opportunity number. Supply at least one. Read this before dicker_transact_opportunity, which converts the opportunity into a real transaction and spends money.

[Dicker Data] Get the extended opportunity projection — Dicker Data's richer view of the same records dicker_get_opportunity_details returns. Filter by partner CSN, contract number, opportunity number or a date window. Dicker Data does not document which extra fields the extended form adds, so compare the two against a real opportunity rather than assuming.

[Dicker Data] List renewal opportunities over a date window. Both ends are required: this API has no paging, so the window is what bounds the response. Dicker Data does not document a date format; send ISO-8601 (YYYY-MM-DD). Narrow further by partner CSN, the Autodesk Customer Service Number. For one opportunity in full, use dicker_get_opportunity_details.

[Dicker Data] Convert an opportunity into a real transaction. THIS SPENDS REAL MONEY against the end customer named in the payload. Read dicker_get_opportunity_details first and have a person approve the line items and prices. The payload is the In block as a JSON object: PartnerPONumber, PartnerPODate, ContractNumber, OpportunityNumber, EndCustomer (Account with CSN, CompanyName, AddressLine1, AddressLine2, City, State, PostCode, CountryCode; ContractManager with FirstName, LastName, Email, Phone, CountryCode), ShipTo, Reseller (CSN and Email), and LineItems (each RenewalSKU, SKUDescription, SerialNumber, Quantity and UnitPrice). Quantities and prices are strings.

[Dicker Data] Change the term on one or more Autodesk contracts. THIS SPENDS MONEY and alters a live contract. Check dicker_get_autodesk_term_switch_status first — Autodesk does not always accept term changes. The payload is the Subscriptions array as JSON; each element takes SubscriptionReferenceNumber and a Contract object carrying Term.