Adds a line item to an existing order.

Creates a new blog post.

Creates a new company location for B2B commerce.

Creates a new customer using GraphQL API.

Creates a new fulfillment.

Creates a new gift card in your Shopify store.

Marks an order as paid by recording a payment transaction for the outstanding amount.

Creates a new product.

Removes one or more tags from a customer.

Updates an existing customer using GraphQL API. Replaces only data that is set.

Updates an existing order.

Updates an existing product. Replaces only data that is set.

Finds customers by email or a search query across multiple fields.

Gets all fulfillment orders for a given order ID.

Searches for Metafields data for a given resource (example order Metafields).

Finds products by searching the titles. Returns individual products.

Finds products by handle. Titles can also be used if handles are not customized.

Finds a product variant by a SKU search.

Finds or creates a specific customer.

Finds or creates a specific product variant by title.

Triggers when a bank account is created or updated.

Triggers when a cash entry is created or updated.

Triggers when a project cost transaction is created or updated.

Triggers when a general journal entry is created or updated.

Triggers when an item is created or updated.

Triggers when a new mail message is sent.

Triggers when a project is created or updated.

Triggers when a purchase entry is created or updated.

Triggers when a quotation is created or updated.

Triggers when a new sales order is created or updated.

Triggers when a subscription is created or updated.

Triggers when a stock position is updated.

Completes a sales order administratively: closes the remaining goods delivery (backorder), the outstanding invoice amount, or both, without delivering or invoicing further. IRREVERSIBLE — per Exact: "Once completed, this action cannot be undone." At least one of Complete Remaining Delivery / Complete Outstanding Invoice must be set to true; this action refuses to send a request in which both are false. Requires the Manufacturing or Wholesale & Distribution package. Not replay-safe by design: re-running on an already-completed order is expected to be refused or ignored by Exact server-side, but this is not live-verified — verify the order status in Exact before re-running.

Creates an account in the system.

Creates a bank account in the system.

Creates a bank entry in the system. Use when rest api is not available in your country.

Creates a cash entry in the system.

Creates a contact in the system.

Creates a cost unit in the system.

Creates a direct debit mandate in the system.

Creates a document attachment in the system.

Creates a general journal entry in the system.

Creates a good delivery in the system.

Creates an opportunity in the system.

Creates a project classification in the system.

Creates a purchase invoice in the system.

Creates a purchase entry line in the system.

Creates a quotation in the system.

Creates a sales invoice line in the system.

Creates a sales item price in the system.

Creates a sales order line in the system.

Creates a DRAFT stock count (header + lines in one request) for a warehouse. The count is always created as a draft (Status 12) — booking the actual stock adjustment is the separate, explicit Process Stock Count action. On every line, provide either Quantity New or Quantity Difference; when both are given, Quantity Difference is used. For warehouses that use storage locations, every line also needs a StorageLocation (via the JSON lines input) — Exact refuses the count without one (live-proven). Requires the Manufacturing or Wholesale & Distribution package — without it Exact Online refuses the request.

Creates a task in the system.

Creates a wbs activity in the system.

Deletes a contact from the system.

Deletes a sales invoice line from the system.

Deletes a sales order line from the system.

Deletes a subscription line from the system.

Downloads a document from the system.

Reconcile ("afletteren") two entries against each other in Exact Online — e.g. a credit note against an invoice, or a payment against an invoice — via the MatchSets XML topic. Re-running a match that already succeeded fails with an Exact "already matched" error — treat that as success, not as a new failure.

Prints a quotation and marks it as Printed (40): Exact creates a document with the printed quotation attached as a PDF (this side effect cannot be disabled). Printing a quotation is required before it can be accepted, rejected or reviewed. This action only creates the printed document and sets the status to Printed — it never emails the customer. Not replay-safe: every successful run creates another printed document in Exact — verify the quotation in Exact before re-running.

Processes a DRAFT stock count: Exact books the stock adjustment and sets the count to Processed (Status 21) with an entry number. ⚠ This is irreversible — the adjustment cannot be undone via the API. Re-running is safe: a stock count that is already processed is skipped automatically, so nothing is ever booked twice. If the step fails with an ambiguous server error, simply re-run it — the built-in check detects whether the count was already processed. Requires the Manufacturing or Wholesale & Distribution package.

Reopens an accepted, rejected or reviewed quotation so it can be changed. Exact enforces this server-side (live-verified): any other status — or a quotation that can no longer be changed, e.g. after conversion to a sales order — is refused with a clear error and nothing changes. After reopening the quotation status is Printed (40), not back to Open. Re-running is safe in practice: an invalid repeat is refused server-side, but verify the quotation status in Exact before re-running.

Sends a sales order in the system.

Updates an account in the system.

Updates a bank account in the system.

Updates a cost center in the system.

Updates custom fields in the system.

Updates an existing goods delivery in Exact Online — set or change the header tracking number (track & trace) and remarks. The shipping method can only be defined when the delivery is created; Exact does not allow changing it afterwards. Re-running with the same input is safe: it re-applies the same values.