Skip to content
LumeFrost · Launch informationChecking

Checking current launch and access information. Review signup access · See plans and limits.

Start Free

Follow LumeFrost

Beta communityon Facebook

Developers / API direction

A considered way
to connect.

A public integration API is planned. We’re defining the boundaries before publishing a contract people can depend on.

Planned · No supported public endpoints
Discuss an integrationProduct documentation
A contract starts with context
01 / IdentityWho is asking?
02 / ScopeWhat belongs to them?
03 / ContractWhat is supported?

Conceptual model · Not an endpoint or working request

Before an API becomes public

Clear boundaries.
Useful documentation.

This page does not issue credentials, provide sample requests or promise integration access. Current customer workflows run through the authenticated product interfaces.

  1. 01

    A real workflow

    Document the task, the owner and the outcome an integration needs to support.

  2. 02

    Explicit permissions

    Keep website owners, website members and platform employees in their own contexts.

  3. 03

    Predictable failure

    Explain requirements, limits and errors so a failed request has an understandable next step.

  4. 04

    A supported contract

    Publish the actual interface and its documentation when it is ready for external use.

Have an integration in mind? Tell us the workflow, the system involved and what success would look like. Leave out keys, tokens and customer data.

Start with the use case