Storefronts & Pixels
Storefront status and marketing pixel configuration.
The merchant’s storefront and the marketing pixels wired into checkout. Storefronts are read-only — status and live URL, never the generated HTML. Pixels are read-write, so an ads integration can provision a pixel without the merchant copying IDs between two dashboards. Scoped keys need storefronts:read and pixels:read / pixels:write.
List storefronts
The merchant's storefronts — status and live URL only (the generated HTML and version history are not exposed). url is the active custom domain when one is set, else the paysio.com subdomain, and null while unpublished. Requires the storefronts:read scope on scoped keys.
https://paysio.com/api/v1/storefrontsAuthorizations
Any API key. Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.
Retrieve pixels
The marketing pixel IDs wired into checkout (Meta, Google Ads, TikTok). Pixel IDs are public identifiers — ad-platform access tokens are never stored here. Returned at the top level (no data wrapper). Requires the pixels:read scope on scoped keys.
https://paysio.com/api/v1/pixelsAuthorizations
Any API key. Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.
Update pixels
Update pixel IDs — lets an ads integration provision a pixel without the merchant copying IDs between dashboards. Send only the fields you want to change: an empty string or null clears a pixel, an omitted field is left alone. Requires the pixels:write scope on scoped keys.
https://paysio.com/api/v1/pixelsAuthorizations
Secret key (sk_*) or app access token. Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.
Body
Meta (Facebook) pixel ID
Google Ads conversion ID (AW-...)
Google Ads conversion label
TikTok pixel ID