Skip to main content

Update Integration Instance

PUT 
/api/temu/:integrationInstance

Updates a Temu integration instance. All body fields are optional — only supply the fields you want to change.

Not yet available to API tokens

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

  • name (string) — new display name.
  • connection_settings (object) — appKey, appSecret, url, accessToken, expiresAt.
  • integration_settings (object) — same fields as on create (start_date, store_id, auto_link_products, auto_create_products, nominal code ids, pricing, inventory, emailCustomers, proforma cost percentages, accounting sync toggles). With PUT the supplied integration_settings object is merged against the stored settings at the top level; PATCH additionally deep-merges nested objects (JSON Merge Patch semantics), except that inventory lists are always replaced wholesale.
  • is_automatic_sync_enabled (boolean).

Side effects when specific settings change:

  • start_date — the instance re-anchors its order sync window.
  • store_id — the linked sales channel is repointed to the new store.
  • pricing.masterOfPrice.name — a background job recalculates cached listing prices.
  • inventory — the channel inventory cache is invalidated and rebuilt.
  • Accounting sync toggles — linked accounting transactions are re-evaluated for sync eligibility.

Authentication: Requires Bearer token.

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