Skip to main content

Update Integration Instance

PUT 
/api/big-commerce/:integrationInstance

Update a BigCommerce integration instance. Supports both PUT (full update) and PATCH (partial update — merges connection_settings and integration_settings with existing values).

Not yet available to API tokens

This endpoint currently requires session authentication; Personal Access Token scope support is in progress.

Authentication: Requires Bearer token.

All fields are optional for PATCH. For PUT, provide all settings fields.

Side effects:

  • If start_date changes, updates the sales channel date
  • If pricing.masterOfPrice changes, dispatches a job to re-cache product listing prices
  • If inventory settings change, invalidates the entire inventory cache
  • If accounting sync settings change, updates related accounting transactions

Requires the integrations.update permission.

Store and sales channel: new orders are created in the store of this connection's sales channel. Whenever the request includes integration_settings.store_id, the sales channel is put in that store if it is in a different one — including when the value equals the saved setting, so re-saving the same store realigns a sales channel that had drifted from it. Nothing is written when the sales channel already uses that store, and orders already imported keep their store. When the sales channel moves, the response adds two top-level keys:

  • message (string): e.g. "Settings saved. New orders will now be created in store 'Curvy AU' — the sales channel was moved from 'Placeholder'."
  • sales_channel_store_updated (object): from and to, each {id, name}; from.id and from.name are null when the sales channel had no store. Both keys are absent when the sales channel did not move.

Request​

Responses​

OK

Response Headers
    Content-Type