Start a project

Developers

Make yourself at home

How our products work, how to run them and how to connect to them.

Docs by product

Pick the system you’re working on

Access Control+ is documented in full. TKT is being written now.

Access Control+

Docs ready

The software that decides who gets in, and the turnstile hardware it runs on. Every claim states what would prove it wrong.

  • 21 chaptersReferenceThe mechanisms a change can break
  • 15 chaptersGuidesDoing the job, on the real screens and at the real gates
  • 2 chaptersConceptsThe arithmetic and the requirements it was shaped by

Software · 23 chapters Hardware · 15 chapters

Open the docs (opens in a new tab)

TKT

Being written

Events, orders, invitations and webhooks.

  • Getting started Planned
  • Events and ticket types Planned
  • Orders and payments Planned
  • Invitations and registration Planned
  • Webhooks Planned
Tell me when it’s ready

Connect your systems

From sandbox to live gates

Anyone can read the docs. Calling the API needs a partner account.

  1. Ask for a partner accountWrite to hello@loft.ug. We set up one account for each organisation, not each person.
  2. Get a sandbox keyBuild against test events, test gates and test tickets before anything reaches a real venue.
  3. Make your first requestPick an event and read its credentials, then follow the guide for the job you’re building.
  4. Go live togetherWe review the integration with you before it reaches a real gate, then issue the live key.
First request
# sandbox key from your partner account
curl https://sandbox.api.loft.ug/v1/events \
  -H "Authorization: Bearer $LOFT_SANDBOX_KEY"

# 200 OK
{
  "data": [
    { "id": "evt_test_8Q2", "name": "Test match", "gates": 4 }
  ]
}

Example: the host, paths and fields are placeholders until the API reference is published

Building on Loft?

Let’s connect the dots

Some things work better together. Tell us what you’re trying to connect.