The Lobo One developer platform
Lobo One runs clubs: their members, what they sell, their courts and rooms, their bookings and their money. The developer platform is how software you write reaches one of those clubs — with that club’s permission, and only as far as it gave you.
How it fits together
Four things, and the order matters because each one is useless without the one before it.
- A developer organization is your company or team in Lobo One. It is created by El Lobo Labs, and it owns everything below.
- An application is a thing you build. Registering one creates the OAuth client it authenticates as and returns its secret once. Registering reaches no club.
- A grant is one club agreeing that your application may act in it, for a named set of scopes. The club creates it. You cannot request one, and there is nothing for an administrator to approve absent-mindedly.
- A call presents your application’s token and names the club it is acting in. What you may do is the grant, narrowed by the scopes on your token, and nothing else.
There is no marketplace and no directory. A club that has never heard of you cannot be reached by anything you do, and a club that has must switch the developer platform on before it can grant anything at all.
What else is here
- Webhooks. Subscribe an application to a club’s events and receive them signed, retried and logged. See Webhooks.
- Logs. Every request your application made and every delivery attempt, for thirty days. See Logs.
- A sandbox. A club that is nobody’s, with synthetic members, that only sandbox applications can reach. See Sandbox.
- A client library. Generated from this API’s own document. See SDK.
The API document
The API publishes its own OpenAPI document at /v1/openapi.json, with an explorer at /v1/docs. It is served by the API to callers the API has authenticated — deliberately, rather than from this page, so that nowhere on a public site is there a box to paste a client secret into.