Administrator
Owns the account
Everything the tier allows, including the team, the billing and the tier itself. Can require multi-factor authentication for the whole partner.
Agencies
Make the SIDES integration a capability you own
You deliver projects for hospitality brands, and sooner or later one of them runs SIDES. Registering as a partner turns that from a subcontract you buy into a service you sell — on documented, versioned ground.
The fit
Learn it once, bill it many times
Agency work against a client’s operational backend is normally a research project with a deadline attached: undocumented endpoints, a contact who leaves, and no way to reuse any of it on the next brief.
SIDES LABS is the opposite arrangement. The specification is public and versioned, the errors have a vocabulary, the changelog tells you what moved, and the knowledge your team builds on the first project is worth the same on the fifth.
Working as a team
Roles, not shared logins
An agency is several people with different jobs. The partner account is built for that, and the roles map to real permissions rather than to etiquette.
Developer
Builds and ships
Apps, versions, changelog entries, statistics and developer resources. No billing, no team management — deliberately.
Accounting
Handles the money
Billing, subscription and invoices, plus a read-only view of the partner profile. Nothing else.
What you get to work with
The material a delivery team needs
- A specification, not a wiki page
-
OpenAPI, written before the handlers, served at
/api/docs, with descriptions, examples and the errors each endpoint can return. - An API changelog
- Every change announced before you meet it. Additions are free and your client must tolerate unknown fields; anything breaking is a new major version.
- Developer resources and a blog
- Guides and worked examples from the people building the platform, published on the same site rather than mailed around.
- A feature-request board
- On the way, with voting, so what you need becomes visible to us and to the other partners asking for the same thing.
- Support and an FAQ
- Being built into the partner area, attached to the account that raised the question, so nobody has to reconstruct the context.
- Marketplace presence
- If what you build is worth selling more than once, list it. Categories, screenshots, ratings and featuring all exist for that.
Can I register on behalf of a client?
A business partner is a company, and the account belongs to whoever the registration names. If the software is yours, register your agency; if the integration belongs to the client, register them and take a developer seat. Ask us if the split is not obvious.
Does a client ever see my other clients?
No. Partner isolation is structural: every partner-scoped query is filtered by the business partner derived from the authenticated principal, server-side, on every request.
Do I have to publish anything?
No. Registering as a partner gives you the API, the documentation and the team roles. A marketplace listing is an option, not an obligation.
What exists today
The platform is being built in the open, and this page describes the platform being built. Today the API authenticates OAuth machine clients and reports the identity, scopes and rate limit of the calling principal. Partner registration and sign-in, the marketplace catalogue, the API changelog, the developer resources, usage statistics and the tier pages come in the phases after it — every commitment above is a commitment, not a screenshot.
Turn one project into a practice
Registration creates your business partner, your first administrator and your tier. You can build and submit long before anything is published.
