Developer documentation

Publish an app on Stayblox

Apps run on your own servers and talk to Stayblox over the Developer GraphQL API. Read bookings and guest data, write results back, embed a page in the host panel, and let hosts install through OAuth.

Build an app Read the full docs

How it works

You build apps as a verified partner and manage them in the Developer section of the Stayblox panel. There is no package to upload here. You declare a manifest, build against the Developer API, test on your own teams, then submit for review. Apps extend Stayblox properties with payments, channel sync, marketing, guest messaging, and more.

🛠️

Create the app

Open the Developer panel, pick a type, and get a Client ID and secret.

🔌

Build the integration

Call the GraphQL Developer API and handle webhooks from your own server.

🚀

Submit and publish

Test with a dev install, submit the manifest for review, then go live.

The path to a published app

Become a verified partner

App publishing is open to verified partners. The same verification gate covers apps and themes.

Publishing & partner access

Create the app in the Developer panel

Open the panel, go to Developer → Apps → New app, and choose a type: remote, payment, channel, or injection. Stayblox issues a Client ID and a Client secret. The secret is shown once and can be rotated.

Getting started

Declare your manifest

Set the scopes, webhook topics, metafields, settings schema, app-page URL, OAuth redirect URIs, and any injections. Manifests are validated on every save.

Manifest reference

Build against the Developer API

When a host installs your app, Stayblox issues per-install credentials: an API token (a Sanctum bearer) and a webhook secret. Call the GraphQL endpoint with the token and verify webhook signatures with the secret.

Scopes

Add OAuth and embedded pages

Let hosts connect from your own site through the OAuth authorization-code flow. Embedded app pages render in the host panel as a sandboxed iframe, signed with your client secret.

OAuth install

Test with a dev install

Install your draft app on a team you own straight from the Developer panel. Dev installs skip review and use your current draft manifest, so you can test API calls, webhooks, the app page, and OAuth.

Dev installs

Submit for review and publish

Submit when the manifest is ready. Submission snapshots it into an app version and runs automated checks, followed by a human review. Once approved, your app is live to hosts.

Review & publishing

App types

Pick a type when you create the app. It decides which manifest fields and protocols apply.

🔌

remote

Remote

Reads and writes data over the API.

💳

payment

Payment

Charges buyers at checkout.

🔄

channel

Channel

Syncs rates and availability.

🧩

injection

Injection

Adds snippets to the storefront.

Your first API call

The Developer API is a single GraphQL endpoint, versioned by date. Send your per-install bearer token and ask who you are.

curl -s https://app.stayblox.com/developer/api/2026-01/graphql \
  -H "Authorization: Bearer $STAYBLOX_APP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{"query":"{ apiVersion currentApp { id name type } }"}'

A valid token returns your app's identity. For the full schema and every mutation, see the GraphQL reference.

What a manifest can declare

✓

Scopes

The access a host consents to at install: read bookings, contacts, rates, payments, and more. Hosts see a plain-language list before approving.

✓

Webhooks

Topics delivered to your server when something changes. Deliveries are thin and signed; you fetch the current state over GraphQL.

✓

Metafields

App-owned data fields on bookings, properties, or contacts. Choose who sees each value: your app, the host, or the guest.

✓

Settings schema

A per-install settings form the host fills in during installation. Values reach your server in session payloads.

✓

Embedded app page

A page rendered inside the host panel as a sandboxed iframe, with a JWT session signed by your client secret.

✓

Payments and channels

Protocol fields for payment and channel apps: session endpoints, capabilities, currencies, and OTA identifiers.

Revenue share

Developers earn fairly from their work.

70%

Developer share

on every sale

30%

Platform fee

hosting, support, marketing

€0

Submission fee

always free to submit

Ready to build?

Create your app in the Developer panel, or read the full reference first.

Build an app Read the docs