Skip to main content

Connect your application to LPData

The workflow has two parts: you manage content with an authenticated account, and your consumer application fetches published content using the Landing Page’s Public ID.

Set the API URL

The LPData API is available at https://api.lpdata.io. The examples use this base URL, without a trailing slash:

Sign in and get a token

Create an account with POST /auth/sign_up or sign in with POST /auth/sign_in. The response contains an access token and a refresh token. See Authentication for the full token lifecycle.
Use the returned access_token for authenticated operations:
Do not put credentials or tokens in public source code or share them. Management operations can only change resources owned by the authenticated user.

Create a Landing Page

Send the Content Document expected by your application. LPData preserves its JSON structure; your application defines how to present that content.
The response includes an id for management and a stable public_id for reads by the consumer application. Use public_id in the public URL; the two identifiers are not interchangeable.

Read published content

The consumer application reads the Content Document without authentication. The response is the document JSON itself, without a wrapping landing_page object:
A successful read returns, for example:
See Landing Pages to manage and read documents, and the API reference for the endpoint list.