15 docs tagged with "Integration"

Overview

What is it?

How does it work?

Overview

Overview

This section covers the programmatic ways to get products into your store and keep them up to date. There are three, and they solve different problems:

Every Publica.la store comes with a default subdomain like yourstore.app.publica.la. You can replace it with your own domain (for example, store.yourcompany.com) so your customers see your brand in the URL.

Add ?embedded=true to any reader URL to render the Publica.la reader inside an iframe in your application. Embedded mode hides navigation controls that would break the parent page context and adapts the UI to fit within a container.

Instant Payment Notifications (IPNs) allow payment processors to communicate directly with your Publica.la store about transaction events. Unlike webhooks, IPNs are sent directly from the payment provider rather than from the Publica.la platform.

The JWT sale webhook is deprecated and will be removed. It keeps working until then, but new integrations should use Webhooks. See Migrate to Webhooks. The sale notification email described below is not deprecated.

An ONIX intake ingests your catalog from an ONIX 3.0 feed. We create an SFTP account and a private storage area for you and send you the password; you upload the feed and the content files there, and we create and update the products in your store from what the feed says. Use it when you are onboarding a large catalog, or when your metadata already flows to distributors and retailers as ONIX.

Overview

Outbound IP Addresses

Overview

Publica.la sends a signed JSON POST request to each of your endpoints when an event it subscribes to happens in your store.