Build on the platform that runs hospitality

SIDES is the API-first backend behind restaurants, outlets, POS systems, kitchens, webshops and delivery. SIDES LABS is where partners build against it: register, develop, submit an app, and reach every operator on SIDES through the marketplace.

Become a partner How the ecosystem works

For integration partners, service providers and agencies building on SIDES.

What this is

A partner platform, not a partner page

SimplyDelivery operates SIDES, the enterprise platform hospitality businesses run their daily operations on. SIDES LABS is the half of it that belongs to everyone else: the place a software company registers as a business partner, builds a service against the SIDES API, and offers it to SIDES customers.

The whole lifecycle lives here — registration and tiers, developer resources, the API changelog, app submission and approval, marketplace presence, ratings, and usage statistics. One account, one contract, one place to look.

Read how the ecosystem fits together

The SIDES LABS wordmark at the centre of a network of connected nodes.

The platform

One API, three audiences, one contract

Everything the portal can do, the API can do — documented, versioned and scoped. A feature that only works through our own interface is a bug, not a shortcut.

Public

Marketplace and developer resources

The catalogue, the API changelog, the developer blog and pricing — readable by anyone, indexed, and served without a single third-party request.

Partner

Your apps, your statistics, your team

An authenticated area per business partner: app submissions, versions, ratings, usage statistics, billing and team management. Partner data never crosses a partner boundary.

SIDES internal

Tiers, approval and editorial

Tier administration, partner administration, app approval, moderation, badges and featuring — every publication step an explicit, recorded transition.

Who builds here

Three ways onto the platform

The route differs, the contract does not. Pick the description that sounds like your company.

Integration partners

You already have a product

A POS, an ERP, a payment provider, a delivery network, a kitchen display. You connect an existing system to SIDES and keep it in sync.

Service providers

You sell a service to operators

Analytics, marketing, staffing, accounting, guest engagement. You build the layer that makes sense of what an operation produces.

Agencies

You build on a client's behalf

You deliver projects for hospitality brands and want the SIDES integration to be a capability you own rather than a subcontract.

The route

How a partner ships

Four steps, in this order. Nothing reaches a SIDES customer without an explicit, recorded approval.

  1. Register the company

    You create a business partner and its first administrator, choose a tier, and confirm your address. Until that is verified the partner is not publicly visible.

  2. Get credentials

    Your integration authenticates as an OAuth 2.0 client and receives a short-lived access token carrying exactly the scopes it was granted.

  3. Build against the API

    One REST contract, one error shape, one set of rate-limit headers. The specification is published, versioned, and never broken underneath you.

  4. Submit and publish

    You submit an app version for review. SIDES approves it, and the listing appears in the marketplace where operators find it.

Getting started

Authenticate, then ask who you are

POST /v1/oauth/token 
curl -X POST https://api.sideslabs.com/v1/oauth/token \
    -H 'Content-Type: application/x-www-form-urlencoded' \
    --data-urlencode 'grant_type=password' \
    --data-urlencode "username=$CLIENT_ID" \
    --data-urlencode "password=$CLIENT_SECRET"

  { "access_token": "…", "token_type": "Bearer",
    "expires_in": 3600, "scope": "publication.changelog:write" }
Which scopes does my client get?

The intersection of the scopes your client is configured with and anything you request. Asking for a scope your client does not hold is not an error — the response tells you what was actually granted, so read scope from the response rather than assuming your request.

How do errors look?

RFC 7807 Problem Details, with a stable code that clients branch on. Never branch on the title or on the status alone.

Can I sign in as a partner user yet?

Not yet. Phase 1 authenticates OAuth machine clients. Partner user registration and sign-in follow in phase 2.

Become a SIDES partner

Registration creates your business partner, your first administrator and your tier. It takes minutes; approval is a separate, recorded step.

Register as a partner Talk to us first