Review and listing
How to submit your app, what ChatBeds reviewers check, what each status means, and how hotels find, connect and disconnect apps.
Before your app appears in every hotel's Apps directory, ChatBeds reviews it. Until then, only your own account can connect it, which is all you need to build and test.
Submitting
On the Developers page, open your app. Under Get listed, press Submit for review. The button needs all of these first:
- a short tagline
- a description
- a category
- a support email
- a privacy policy address
- an install address (where Connect sends hotels)
- a redirect address
- at least one scope
If any is missing, ChatBeds tells you which ones. You can submit an app that is a Draft or that needs changes.
What reviewers check
- An honest listing. The name, tagline and description say what the app really does for a hotel, and what it does with the hotel's data.
- A real privacy policy at the address you gave, covering guest data.
- The fewest scopes. Each scope you ask for is used by a feature the listing describes. See Scopes.
- A working support email that a hotel can write to.
- A working install address. Pressing Connect leads, through your page, to the ChatBeds consent screen and back to a working app.
The going live checklist covers these and more.
Statuses
| Status | Shown as | What it means |
|---|---|---|
DRAFT | Draft | New, or restored after a suspension. Only your account can connect it |
IN_REVIEW | In review | Waiting for ChatBeds. Only your account can connect it; connections it already has keep working |
LISTED | Listed | In every hotel's Apps directory. Any hotel can connect it |
REJECTED | Changes needed | ChatBeds left a note saying what to change. Fix it and submit again |
SUSPENDED | Suspended | Stopped by ChatBeds. Every token stops at once, the app can't be connected, and you can't change it |
Asking for more scopes
If a Listed app adds scopes, it goes back to In review. Its existing connections keep working with what each hotel already allowed. Removing scopes doesn't need a review.
Suspension
ChatBeds can suspend an app at any time, with a note saying why. When it does:
- every access token stops at once (
401), and/oauth/tokenanswersinvalid_client; - hotels see "ChatBeds has suspended this app. It cannot use your data until it is restored." on their Apps page;
- connections are kept, so if ChatBeds restores the app, they work again. A restored app goes back to Draft.
Write to contact@chatbeds.app to talk about a suspension.
How hotels find and connect apps
Hotel owners and admins open Apps in the ChatBeds dashboard. The page has two parts.
App directory shows every listed app as a card: name, category, tagline, description, "It asks to:" with the scope labels, a Connect button that opens your install address, and a Website link.
Connected apps shows the apps connected to the hotel's properties: which property, when and by whom it was connected, when it was last used, and what it may do.
The hotel's plan must include the partner API to connect apps from other developers.
Disconnecting
A hotel presses Disconnect next to a connected app, then Yes, disconnect. Your app's access to that property ends at once: its tokens and its key stop, and webhooks for that property are no longer sent.
ChatBeds doesn't notify your app. You'll get 401 on your next call and invalid_grant when you refresh. Treat that as "disconnected" and stop syncing that property. If the hotel connects again later, you get a new code and new tokens.
Building something?