Connect Uplisting to ChatGPT.
Ask your Uplisting bookings, guests, and calendar questions in plain English. This guide shows the self-serve path first, then explains when Axelrod is the managed option.
For Short-term rental operators and small agencies running their portfolio in Uplisting.
By Axelrod Labs · Updated June 2026
Ask Uplisting operational questions without opening another dashboard.
Arrival board grouped by listing and OTA (Airbnb, Booking.com, Vrbo, direct).
Recent booking changes with check-in date, guest, and property.
Gap-night list across properties for revenue follow-up.
Booking totals by property and channel.
ChatGPT uses a small private web connection to ask Uplisting read-only questions. You own that connection; it only talks to Uplisting when you ask ChatGPT something.
Connecting Uplisting to ChatGPT
Yes, when you keep it read-only. Your Uplisting API key stays in a private connection you control, not inside ChatGPT, and this setup only reads data; it cannot create, change, or cancel reservations. Remove the ChatGPT app and delete the private connection to revoke access at any time.
Three things: a paid ChatGPT plan with Developer mode (or custom MCP connectors) enabled, Uplisting admin access to obtain Uplisting API key, and a free Cloudflare account for the private connection.
No. This guide sets up a read-only connection, so ChatGPT can answer questions about your Uplisting bookings, guests, and calendar but cannot modify anything.
Plan on about 45-90 minutes if your Uplisting API key is ready. It can take longer when Uplisting requires API approval, partner access, or workspace admin approval before ChatGPT can scan the connector.
Most common Uplisting issue: the API key is pasted raw instead of Base64-encoded for HTTP Basic auth, returning 401 Unauthorised. Uplisting authenticates with HTTP Basic auth using the Base64-encoded API key (Authorization: Basic <base64(api_key)>). A raw, un-encoded key returns 401 Unauthorised.
Have these ready.
Budget about an hour for connector setup once credentials are ready. Add more time if you need API approval, partner access, or workspace admin approval.
Keep the first version boring and read-only.
Connect Uplisting to ChatGPT in 4 steps.
Get your Uplisting credentials
- Open Uplisting with an account that can access Connect settings.
- Go to Connect > API at app.uplisting.io/connect/api and generate an API key.
- Copy the key and confirm it reads bookings and properties (the public API excludes guest inbox/messaging).
Set up the private connection
- Use a private Cloudflare Worker or managed setup path so PMS credentials stay outside ChatGPT.
- Paste your Uplisting API key into the prompted fields.
- Deploy the private connection and open the generated health page.
- Confirm it says Connected to Uplisting before continuing.
Add it to ChatGPT
- Open ChatGPT settings.
- Go to Apps, open Advanced settings, and enable Developer mode.
- Create a custom app from the remote server URL shown on the health page.
- Complete the OAuth authorization screen.
Try operational prompts
- Open a new chat and select the app from Developer mode.
- Start with arrivals, departures, missing guest details, and occupancy questions.
Start with operational questions, not vague chatbot prompts.
Expected result: ChatGPT should answer with specific Uplisting records: property names, reservation dates, guest fields it is allowed to read, and a clear note when data is missing.
Good for one property. Thin for a real portfolio.
ChatGPT can answer Uplisting questions. Axelrod turns the same booking data into morning briefs, guest-message drafts, cleaner handoffs, pricing nudges, and an approval queue across your stack.
Talk to AxelrodCheck Uplisting's current API docs before connecting anything.
PMS settings and API permissions change. Use these links to confirm the exact credential names in the account you are working with.
Uplisting issues first, generic OAuth issues second.
Uplisting authenticates with HTTP Basic auth using the Base64-encoded API key (Authorization: Basic <base64(api_key)>). A raw, un-encoded key returns 401 Unauthorised.
Keys are environment-specific (staging vs production use a different base domain); using the wrong environment's key fails against the wrong data.
Most common Uplisting issue: the API key is pasted raw instead of Base64-encoded for HTTP Basic auth, returning 401 Unauthorised.
Developer mode is missing: confirm the ChatGPT account or workspace can create custom apps, and ask the workspace admin if the option is hidden.
OAuth popup blocked: allow popups for ChatGPT, then reconnect the app.
The app returns empty results: check that the PMS user or token can read all properties, reservations, and guests.
The app returns unauthorized: rotate the PMS credential, redeploy the private connection, then reconnect ChatGPT.