Skip to main content
Drop zones let you place an external app in a configured area of Fluid Admin, checkout, or order confirmation. Fluid renders the app from its external URL, so you can extend an experience without changing the surrounding Fluid page.

​
Choose the right surface

Use Fluid Admin to create, update, activate, and place drop zones for your company. There is no generated reference for the management surface. Its current contract is not reliable enough to publish, so do not treat it as a supported external integration contract. For a direct REST integration, use List drop zones. It is the canonical public Checkout reader. The FairShare SDK uses its own SDK-internal List public drop zones reader. If you are building a direct REST integration, use the Checkout reader instead. Both public readers expose active zones for checkout and order-confirmation experiences.

​
Embed external content safely

Each drop zone renders content from an external embed URL. Keep your embed responsive, accessible, and able to fail without blocking the surrounding page.

​
Handle context by surface

Checkout embeds receive context for the current cart. Admin detail embeds can receive signed context for the record beside them. These contexts are not interchangeable. Treat every context token as sensitive, validate it on your server, and do not infer broader API access from it.