Skip to main content
Update an existing store’s name, status, or configuration settings. Only fields included in the request body are updated; omitted fields remain unchanged.
Authentication: API Key (owner or admin role required)
This endpoint does not manage webhook configuration. If a webhookSettings field is sent in the request body it is silently ignored and the response includes a top-level warnings array; other fields update normally and the call returns 200. Use add-webhook, update-webhook, and remove-webhook to configure webhooks, and GraphQL Store.storeWebhooks to list them.

Request Body

Notification Settings

Two categories with different write permissions: Merchant-writable (✅ accepted via this endpoint): Platform-managed (🔒 read-only via merchant API; managed by PANCAKE platform):
If your notificationSettings payload includes any platform-managed field (email*, or the legacy notifyPayoutCompleted / notifyPayoutFailed keys — payout result emails are always delivered and have no toggle), the server silently drops it and returns a 200 response with a warnings[] entry listing the dropped keys. To toggle a customer email, contact PANCAKE platform support.

Checkout Settings

Checkout Theme Settings (applies to both light and dark):

Partial Update Semantics

Both settings objects support partial updates. Each sub-field follows these semantics: Setting the entire object to null (e.g., "notificationSettings": null) clears all fields in that settings group.

Example Request

Success Response (200)

Response Fields

Same as Create Store response fields. Verification-managed (🔒 read-only via this endpoint; returned for reference only):
supportEmail and website cannot be set through this endpoint. Each is written automatically once the merchant completes support-email verification or product-domain verification for a store with production enabled (prodEnabled: true). A request that includes either field returns 200 with the store unchanged and no warnings entry — the field is dropped silently.

webhookSettings Compatibility Warning

If a webhookSettings field is sent in the request body, it is silently ignored and the response includes a top-level warnings array. The data.store object is unaffected.

Errors

Retry policy: Never retry 4xx — fix the request and resubmit. Retry 5xx with exponential backoff (start 5s, max 3 attempts).