Developers

Your platform shouldn't choose
your frontend.

Build with React, Next.js, Web Components, native apps or whatever comes next. YLP stays underneath as the structured operational core.

API-first

One backend for every delivery layer.

Content, catalogue and commerce operations stay central while each frontend can be built for its own channel.

REST

Predictable endpoints

Public content, commerce, checkout, forms and operational APIs.

GRAPHQL

Flexible data queries

Use GraphQL for clients that need composable query shapes.

OPENAPI

Explore the contract

API documentation and explorer support for implementation teams.

SDK

JavaScript + PHP

SDK-friendly integration paths for common development stacks.

EVENTS

Webhooks

Trigger downstream actions when content or commerce changes.

SECURITY

Keys + bearer auth

Secure public and customer-facing API access patterns.

Example

Fetch content. Render anywhere.

Use structured content from YLP in your own application without inheriting a template engine or storefront theme.

01Preview and publish-aware content
02Customer JWT support for commerce flows
03Payment and checkout endpoints
04Forms, newsletters and plugin runtime APIs
example.tsapi.yourlocalpage.com
const response = await fetch(
  'https://api.yourlocalpage.com/api/public/v1/pages/home',
  {
    headers: {
      'x-api-key': process.env.YLP_PUBLIC_KEY
    }
  }
);

const { data } = await response.json();
renderPage(data);

Bring the frontend you want.

Use YLP as the content, commerce and operations backend underneath it.

API / DELIVERY SURFACEAVAILABLE
01REST + GraphQLStructured platform access
02WebhooksReact to business events
03Frontend freedomUse the stack you choose
BUILD YOUR WAY / KEEP ONE BACKEND