MCP Tool Reference (Partner)

Tools available to partner accounts. Every tool here mirrors the equivalent Partner REST API endpoint (partner-v1) and is named with a partner_ prefix. For merchant accounts see the Tool Reference (Merchant).

Access indicates the minimum permission required:

Read — any read-capable partner role (marketplace_partner:read or single_merchant_partner:read scope for M2M keys)
Write — a write-capable partner role (marketplace_partner:write or single_merchant_partner:write scope for M2M keys)

Both partner types — marketplace and single-merchant — get the same tools. What differs is data ownership: under marketplace, buyers belong to the partner and share one credit line across sub-merchants; under single-merchant, each sub-merchant owns its own buyers and credit lines. This changes how merchant_id behaves on some tools, noted below. See the Partner API Integration guide.

list_resolve_accounts returns a partner_type of marketplace or single_merchant on the account — call it first to know which rules apply.

General

These tools are shared with merchant accounts and are not partner_-prefixed.

Tool	Access	Description
`list_resolve_accounts`	Read	List the Resolve accounts available to the authenticated login. Call this first when a login has access to multiple accounts.
`search`	Read	Semantic search over Resolve's published help articles — ask "how does X work in Resolve".
`create_temp_file`	Write	Mint a presigned S3 upload URL for a file (e.g. an invoice PDF) so it can be attached to an invoice without passing the file through the LLM. Not available in ChatGPT or Codex — see note below.
`list_temp_files`	Read	List previously uploaded temp files and mint fresh download URLs. Not available in ChatGPT or Codex — see note below.

File handling in ChatGPT and Codex: these clients attach files directly to the conversation instead of using the temp-file tools. Tool parameters that expect a file URL (such as merchant_invoice_url on partner_create_invoice) accept the conversation attachment directly, and the MCP server resolves it for the Resolve API. The temp-file tools are hidden for these connections.

Sub-merchants

The merchants beneath your partner account. These endpoints have no merchant-API equivalent.

Tool	Access	Description
`partner_list_merchants`	Read	List the sub-merchants under the partner account.
`partner_get_merchant`	Read	Fetch a single sub-merchant by ID.
`partner_create_merchant`	Write	Create a new sub-merchant under the partner account.
`partner_update_merchant`	Write	Update a sub-merchant's details.

Customers

Tool	Access	Description
`partner_list_customers`	Read	List customers across your sub-merchants, with exact-match filters on `business_name`, `email`, and more.
`partner_get_customer`	Read	Fetch a single customer, including credit status and available credit.
`partner_create_customer`	Write	Create a new customer (buyer). Single-merchant partners must pass `merchant_id` for the owning sub-merchant; marketplace partners must omit it — the customer belongs to the partner.
`partner_update_customer`	Write	Update a customer's details.
`partner_create_customer_document`	Write	Attach a supporting document to an existing customer using a presigned upload or remote download. Requires partner write access.
`partner_request_credit_check`	Write	Submit a customer for credit underwriting.
`partner_enroll_customer`	Write	Enroll an approved customer in net terms.

Customer supporting documents

Find or create the customer first, then call partner_create_customer_document with its ID as merchant_customer_id. This is separate from customer creation and is available to partner accounts; regular merchant v5 tools do not expose it.

Supply document_type, filename (including extension), and filetype (matching MIME type). Supported types are bank_statements, credit_references, financial_statements, payment_history, and other. Bank statements require PDF; other types accept PDF, PNG, JPEG, CSV, XLS, or XLSX.

ChatGPT: pass the conversation attachment as download_url, with filename and filetype supplied separately. The MCP adapter resolves the attachment URL and Resolve queues a remote download.
Claude / other clients: omit download_url to receive a presigned upload_url. PUT the bytes to that URL before upload_expires_at, including all returned upload_headers. Alternatively, pass an already hosted public HTTP(S) URL as download_url.

additional_data_request_id is optional only for bank_statements and must refer to an open banking-data request for the same customer.

Keep the returned document_id. Transfer and validation are asynchronous; a successful response does not confirm validation. In remote-download mode, check queue_dispatch_status: queued means dispatched, while failed signals a dispatch failure even with HTTP 200. The response has no status field, and customer credit status alone does not prove that this document validated.

See the Partners API document endpoint for the full request and response contract.

Invoices

Tool	Access	Description
`partner_list_invoices`	Read	List invoices across your sub-merchants, with filters on number, PO number, customer, balance, and status.
`partner_get_invoice`	Read	Fetch a single invoice.
`partner_create_invoice`	Write	Create an invoice for a customer. `merchant_id` is required — the sub-merchant the invoice belongs to.
`partner_update_invoice`	Write	Update an invoice (e.g. set `terms` and `advance_requested` before sending).
`partner_send_invoice`	Write	Send the invoice to the customer.
`partner_capture_invoice`	Write	Capture an authorized invoice.
`partner_void_invoice`	Write	Void a sent invoice.
`partner_cancel_invoice`	Write	Cancel an invoice.
`partner_delete_invoice`	Write	Delete a draft (unsent) invoice.
`partner_delete_invoices`	Write	Delete several draft invoices in one call.

Orders

Partner API keys hold no order write permissions, so only reads are available.

Tool	Access	Description
`partner_list_orders`	Read	List orders.
`partner_get_order`	Read	Fetch a single order.

Charges

Partner API keys hold no charge write permissions, so only reads are available.

Tool	Access	Description
`partner_list_charges`	Read	List charges.
`partner_get_charge`	Read	Fetch a single charge.

Shipments

Tool	Access	Description
`partner_list_shipments`	Read	List shipments.
`partner_get_shipment`	Read	Fetch a single shipment.
`partner_create_shipment`	Write	Add a shipment (tracking number, courier, fulfillment method) to an invoice.
`partner_update_shipment`	Write	Update a shipment.
`partner_delete_shipment`	Write	Delete a shipment.
`partner_sync_shipment_tracking`	Write	Pull real-time tracking status from the courier.
`partner_get_shipment_signed_upload_url`	Write	Mint a signed URL for uploading proof-of-delivery files, required for non-shipping-provider fulfillment methods.

Payments & Payouts

Tool	Access	Description
`partner_list_payments`	Read	List payments received from customers.
`partner_get_payment`	Read	Fetch a single payment, including which invoices it applied to.
`partner_create_payment`	Write	Record a payment against an invoice.
`partner_list_payouts`	Read	List payouts from Resolve.
`partner_get_payout`	Read	Fetch a single payout.
`partner_list_payout_transactions`	Read	List individual transactions within payouts.
`partner_get_payout_transaction`	Read	Fetch a single payout transaction.

Credit Notes

Tool	Access	Description
`partner_list_credit_notes`	Read	List credit notes.
`partner_get_credit_note`	Read	Fetch a single credit note.
`partner_create_credit_note`	Write	Issue a credit note against a sent invoice.
`partner_void_credit_note`	Write	Void a credit note.

Webhooks

Tool	Access	Description
`partner_list_webhooks`	Read	List webhook endpoints and their subscribed events.
`partner_upsert_webhook`	Write	Create or update a webhook endpoint and its subscribed events.
`partner_delete_webhook`	Write	Delete a webhook endpoint.