Skip to content
Livstick Developers
v3 Request access

Access and environments

There is no self-serve signup for the Client API. Livstick issues credentials to approved teams and partners directly, and everything below describes what you get once that happens.

Before you begin

Credentials are issued by the Livstick team, not created through a form on this site. If you don’t have one yet, request developer access

Requesting access

Access is granted to approved teams and partners, one key at a time. Reach out with what you are building and which API you need, and a key is issued for your account — there is no waiting list or tiered plan to pick from.

What you receive

A key comes back, along with the facts that decide what it can do and where it works. The key's form on the wire differs by API, but what it carries does not.

What comes with a key
Item What it means
A key Sent as Authorization: Bearer liv_<prefix>_<secret> for the v3 API, or in the URL path itself for the 2.1 API — the same underlying key, presented differently by each API.
Scopes The set of operations the key is allowed to perform. v3 grants scopes per operation family (containers:read, messages:write, and so on); 2.1 grants client_v2 or user_v2 per route family.
A platform constraint A key can be limited to a single platform in addition to its scopes.

Key lifecycle

A key is not a static string handed over once. It carries state that changes over time, tracked the same way regardless of which API it targets.

  • Expiration — a key can carry an expiration date.
  • Status — active, revoked or expired, checked on every request.
  • Audit — every use is recorded.
  • lastUsedAt — kept up to date each time the key is used.

Base URLs

The v3 API is served from a fixed, public base URL. The 2.1 API is not — its base is part of what you receive with access.

text 
v3   https://client-api.v5.livstick.com/api/v3
2.1  provided with your access — not published here

Sandbox and test data

There is no public sandbox environment for either API in this documentation. Every example on this site is meant to be read against the base URLs above, using credentials issued to you.