Live Me Up API (0.0.2)

Download OpenAPI specification:Download

technical support: tech@livemeup.io

API you can use to manage your Live Me Up resources

landing-page

Live Shopping page configuration

Get displayed lives and replays

Get displayed lives and replays

header Parameters
x-livemeup-tenant-name
required
string (TenantNameHeader)
Example: shopname.myshopify.com

The unique tenant name. For Shopify shops it is in the format of "shopname.myshopify.com"

Responses

Response samples

Content type
application/json

Example of a response when tenant displays one upcoming live and two replays

{}

Get displayed live and replays (v1) Deprecated

Get displayed live and replays. This endpoint is deprecated, please implement the v2 instead.

header Parameters
x-livemeup-tenant-name
required
string (TenantNameHeader)
Example: shopname.myshopify.com

The unique tenant name. For Shopify shops it is in the format of "shopname.myshopify.com"

Responses

Response samples

Content type
application/json

Example of a response when tenant display one upcoming live and two replays

{}

event-reminders

Subscribe a phone number to an event SMS reminder

Create an SMS reminder for an event

Register a phone number to receive an SMS reminder before an event starts. Idempotent on (eventId, phoneNumber).

path Parameters
eventId
required
string <uuid>
Example: 86ac818d-6eae-43c0-982e-d9c74200a230

The event the reminder is created for

header Parameters
x-livemeup-tenant-name
required
string (TenantNameHeader)
Example: shopname.myshopify.com

The unique tenant name. For Shopify shops it is in the format of "shopname.myshopify.com"

Request Body schema: application/json
commercialInfoConsent
required
boolean
eventURL
required
string

Should be the URL of the page, will be included in the sent SMS

firstName
required
string
locale
required
string
phoneNumber
required
string

Responses

Request samples

Content type
application/json
{}

Intelligence Cloud

HMAC-SHA256 authenticated endpoints for Intelligence Cloud to access replay transcripts and chat messages. Authentication uses a canonical string format: {METHOD}\n{PATH}\n{SORTED_QUERY}\n{BODY}\n{TIMESTAMP}. The HMAC-SHA256 digest is sent in the x-ic-signature header, and the timestamp in the x-ic-timestamp header.

List replays with data readiness

List available replay events for a given tenant with data readiness statuses (transcript and chat export availability)

query Parameters
tenant
required
string
Example: tenant=storename.myshopify.com

The tenant name to list replays for

since
required
string <date-time>
Example: since=2026-03-01T00:00:00Z

ISO 8601 date — only replays with startTime >= since are returned. Must be within the last 60 days.

header Parameters
x-ic-signature
required
string

HMAC-SHA256 signature of the canonical request string

x-ic-timestamp
required
string

ISO 8601 timestamp of the request — must be within ±5 minutes of server time

Responses

Response samples

Content type
application/json
[
  • {
    }
]

Export replay data and get signed URLs

Trigger export of chat messages and return signed URLs for both chat and transcript files. If the chat export already exists, the upload is skipped (idempotent). Signed URLs expire in 1 hour.

path Parameters
replayId
required
string
Example: evt-123

The replay event ID to export data for

header Parameters
x-ic-signature
required
string

HMAC-SHA256 signature of the canonical request string

x-ic-timestamp
required
string

ISO 8601 timestamp of the request — must be within ±5 minutes of server time

Responses

Response samples

Content type
application/json