ConnectWise Manage

Get a specific activity by ID.

Get an inventory adjustment header together with every one of its detail lines. Use this to check an adjustment before posting it with cw_close_adjustment, and to read back the unitCost ConnectWise applied to each line. The header's closedFlag tells you whether it has already posted.

Get a specific finance agreement by ID.

Get additions (line items) for a specific agreement.

Get the billing recap for a specific agreement by agreement ID.

Get a specific catalog item by ID.

Get a specific company by ID.

Get a specific configuration item (asset/CI) by ID.

Get a specific contact by ID.

Report every catalog item holding non-zero stock, one row per warehouse bin. Negative on-hand is reported too, because a negative balance is exactly what an adjustment usually has to correct. ConnectWise exposes on-hand only per bin, so this walks every bin and pages each one fully, which makes a whole-instance scan slow: pass warehouseId or binIds to narrow it. Each row gives the catalog item ID, identifier and description, the warehouse and bin, the on-hand quantity, the unit cost and the extended value, plus any serial numbers held in that bin. Read the cost with care: the ConnectWise API e…

Get a specific invoice by ID.

Get a specific member by ID.

Get a specific sales opportunity by ID.

Get a specific procurement product item by ID.

Get a specific project by ID.

Get a specific project ticket by ID.

Get all notes on a project ticket, including notes from any child tickets.

Get a specific purchase order by ID.

Get the line items on a specific purchase order, including unit cost, extended cost, quantity received, and receipt status.

Get a specific sales order by ID.

Get the procurement product items on a specific sales order. Always scoped to the given order; any extra 'conditions' are ANDed with that scope.

Get a specific service ticket by ID.

Get configuration references associated with a service ticket, one page at a time (default: page 1, 25 results). Request additional pages as needed. Returns id, deviceIdentifier, and _info when provided by Manage; use cw_get_configuration for full configuration details.

Get all notes/discussions on a service ticket, including notes from any child tickets.

Get a specific time entry by ID.

List inventory adjustment types in ConnectWise Manage. Every adjustment header names one, so call this before creating an adjustment. Each type carries an identifier, a name and an auditTrailFlag. The type is what tells ConnectWise which general ledger account the adjustment posts against, so pick it deliberately rather than taking the first row.

List service boards in ConnectWise Manage.

List product categories from the ConnectWise catalog.

List product subcategories from the ConnectWise catalog.

List the communication types configured in this ConnectWise tenant (GET /company/communicationTypes). Records include id, description, emailFlag, phoneFlag, faxFlag, and defaultFlag. Use the ids as emailTypeId / phoneTypeId on cw_create_contact, or as type { "id": <id> } in communicationItems on cw_update_contact.

List manufacturers referenced by catalog items.

List ticket priorities in ConnectWise Manage.

List schedule statuses in ConnectWise Manage. Statuses are usually 'Tentative' and 'Firm', one of which is flagged as the instance default.

List schedule types in ConnectWise Manage. The type decides what kind of object the entry books against, so call this before creating an entry. Typical identifiers are 'S' for Service (a service ticket), 'P' for Project, 'C' for Sales and 'N' for Meeting.

List ticket statuses for a specific service board in ConnectWise Manage.

List warehouse bins in ConnectWise Manage. A bin is the location stock actually sits in, and every inventory adjustment line names one. Pass warehouseId to list only the bins of a single warehouse. The quantityOnHand on a bin is a rollup across every item in it, so use cw_get_inventory_on_hand for per-item stock.

List inventory warehouses in ConnectWise Manage. A warehouse groups the bins that actually hold stock, so start here before reading on-hand quantities or building an adjustment. Each warehouse carries name, location, department, currency and the inactiveFlag / lockedFlag pair: a locked warehouse rejects adjustments.

Search schedule activities in ConnectWise Manage.

Search agreement recaps — the billing rollup ConnectWise computes per agreement: starting, used, remaining, available and overrun amounts, unbilled periods, and the last and next invoice amount and date. Use this to answer agreement burn-down and overage questions without adding up additions by hand.

Search finance agreements (recurring revenue contracts) in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "cancelledFlag = false", "company/name = 'Acme'").

Search the ConnectWise product catalog. Use 'conditions' for CW query syntax (e.g. "identifier like '%SKU-%'" or "manufacturer/id=5").

Search companies in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "name like '%Acme%'").

Search configuration items (assets/CIs) in ConnectWise Manage.

Search contacts in ConnectWise Manage. Parent fields go in conditions with double-quoted strings (e.g. firstName = "John" or company/id = 5). There is no contact field named name — use firstName and lastName (a bare name = "..." is rewritten to those). Contact type is a child collection: do not put types or types/name in conditions (Manage returns 400 ApiFindCondition). Filter type with typeName, typeId, or childConditions such as types/name = "Primary". Single quotes are accepted and sent as double quotes.

Search invoices in ConnectWise Manage.

Search members (technicians/users) in ConnectWise Manage.

Search sales opportunities in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "status/name = '1. Open'", "closedFlag = false").

Search opportunity forecasts/revenue items for a specific opportunity.

Get notes on a specific sales opportunity.

Search procurement product items — catalog SKUs placed on a ticket, project, sales order or opportunity, with their own price, cost and margin. For the catalog SKU definitions themselves use cw_search_catalog_items instead. Use 'conditions' for CW query syntax (e.g. "company/id = 42", "invoice/id = 1001").

Search tickets under a project. Use projectId to filter by project, or conditions for CW query syntax.

Search projects in ConnectWise Manage.

Search purchase orders (the buy side) in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "closedFlag = false", "vendorCompany/name = 'Ingram'", "poDate > [2026-01-01T00:00:00Z]").

Search sales orders (the sell side) in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "status/name = 'Open'", "company/name = 'Acme'"). For purchase orders use cw_search_purchase_orders instead.

List sales pipeline stages in ConnectWise Manage.

Search schedule entries (booked resource time) in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "member/id = 147 and type/id = 4"). Each entry carries objectId (the ticket, activity or project ticket it is booked against), member, dateStart, dateEnd, type, status, reminder, doneFlag and hours. ConnectWise interprets dateStart and dateEnd as UTC (trailing 'Z'). Perth (AWST) is UTC+8 with no daylight saving, so 10:00 Perth is 02:00Z and a Perth time before 08:00 lands on the previous UTC date.

Search service tickets in ConnectWise Manage. Use 'conditions' for CW query syntax (e.g. "status/name != 'Closed'" or "company/name = 'Acme'").

Search time entries in ConnectWise Manage.

Test the connection to ConnectWise Manage.

Update an agreement addition (recurring line item) with JSON Patch (Manage PATCH /finance/agreements/{agreementId}/additions/{additionId}). Use this for seat-count reconciliation and similar corrections. Common paths: quantity, effectiveDate, cancelledDate, billCustomer ('Billable' | 'DoNotBill' | 'NoCharge'), description, invoiceDescription, unitPrice, unitCost. Set dryRun to preview the result without saving.

Update an existing catalog item using JSON Patch operations.

Update an existing company using JSON Patch operations.

Update an existing contact with JSON Patch (Manage PATCH /company/contacts/{id}). Operations use the same shape as cw_update_ticket and cw_update_company: op (replace, add, or remove), path, and value. Add and replace require value. Common paths: firstName, lastName, title, inactiveFlag, site (value is { "id": <siteId> }), communicationItems (email and phone — replacing the array replaces every item, so include items to keep; each item is { "type": { "id": <communicationTypeId> }, "value": "...", "communicationType": "Email" } or communicationType "Phone". Communication type names vary per ten…

Add or remove a contact type association (Manage POST or DELETE /company/contacts/{id}/typeAssociations). Use this instead of cw_update_contact when tagging a contact, for example as Decision Maker after they authorize someone in a ticket note. action "add" takes typeName or typeId. typeName is resolved with GET /company/contacts/types. Adding a type the contact already has returns the existing association and does not create a duplicate. action "remove" takes associationId, or typeName / typeId to find the association and delete it.

Update a single finance invoice with JSON Patch (Manage PATCH /finance/invoices/{id}); returns the updated invoice (same shape as cw_get_invoice). Allowed paths (with or without leading slash): status/id (numeric id) or status ({ id }); attention, dueDate, date, reference, customerPO, internalNotes; billToCompany and billingSite (as { id }) or their /id subpaths (billToSite is accepted as an alias for billingSite). Manage invoices have no billToContact field; use attention for the contact name. Any other path (custom fields, payment fields, etc.) is rejected before Manage is called. Scout bill…

Update an existing schedule entry using JSON Patch operations. Use this to move a booking, change its status, or mark it done. There is deliberately no delete tool: removing booked time stays a manual action in ConnectWise. ConnectWise interprets dateStart and dateEnd as UTC (trailing 'Z'). Perth (AWST) is UTC+8 with no daylight saving, so 10:00 Perth is 02:00Z and a Perth time before 08:00 lands on the previous UTC date.

Update an existing service ticket using JSON Patch operations.

Add or remove configuration associations on a service ticket. Operations run sequentially in the supplied order, including repeated configuration IDs. Removing an association leaves the configuration object intact. Continues after individual failures without rollback or automatic retries; returns every operation's outcome and sets isError if any fail. Duplicate-add and missing-association errors are reported as failures.

Update a time entry with JSON Patch (Manage PATCH /time/entries/{id}). Use this to correct a mistaken entry, including actualHours on a metered agreement (those hours round to 0.25). Paths are field names such as actualHours, notes, internalNotes, timeStart, timeEnd, or billableOption. Billed entries may be rejected by Manage.