Update Customer Matching Configuration

PUT 
/api/qbo/integration-instances/:integrationInstance/matching-config

Save the customer matching configuration for a QuickBooks Online integration instance. The full configuration must be sent - all fields except generic_local_parts are required.

Authorization

Any valid API token can call this endpoint — no specific scope required. Manage tokens.

Validation rules beyond per-field types:

• The five weights must sum to more than 0.
• thresholds.review must be less than or equal to thresholds.auto.
• generic_email_handling must be one of demote, ignore, accept.

The saved configuration is used by subsequent match runs and previews (each run also stores a snapshot of the configuration it was scored with). Saving the configuration does not modify anything in QuickBooks.

Returns the normalized configuration that was saved. Returns 404 if the integration instance does not exist.

Authentication: Requires Bearer token.

Request

Responses

200

OK

Response Headers

Content-Type

401

Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.

403

Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.

404

Not Found

Response Headers

Content-Type

422

Unprocessable Entity

Response Headers

Content-Type

429

Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.