Connect Tokeet to ChatGPT.
Ask your Tokeet 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 Vacation-rental hosts and property managers running multi-channel listings in Tokeet.
By Axelrod Labs · Updated June 2026
Ask Tokeet operational questions without opening another dashboard.
Arrival board grouped by property and booking channel (Airbnb, Booking.com, Vrbo, direct).
Recent reservation activity with check-in date, guest, rental, and channel.
Gap-night list across rentals for revenue follow-up.
Reservation totals by rental and channel.
ChatGPT uses a small private web connection to ask Tokeet read-only questions. You own that connection; it only talks to Tokeet when you ask ChatGPT something.
Connecting Tokeet to ChatGPT
Yes, when you keep it read-only. Your Tokeet account ID and 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, Tokeet admin access to obtain Tokeet account ID and 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 Tokeet bookings, guests, and calendar but cannot modify anything.
Plan on about 45-90 minutes if your Tokeet account ID and API key is ready. It can take longer when Tokeet requires API approval, partner access, or workspace admin approval before ChatGPT can scan the connector.
Most common Tokeet issue: a 401 because the account ID and API key are swapped, or only the API key was supplied without the account query parameter. Tokeet's Client API needs both the account ID (sent as a query parameter, e.g. ?account=YOUR_ID) and the API key (sent in the Authorization header). Supplying only one fails with a 401 'check your apikey and account id' error.
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 Tokeet to ChatGPT in 4 steps.
Get your Tokeet credentials
- Sign in to Tokeet as the account owner or an admin.
- Open Settings > Account Info and copy your Account ID (shown under the Account Info header; include the digits after the dot).
- Generate an API key for the account and confirm it can read bookings, guests, and rentals.
Set up the private connection
- Use a private Cloudflare Worker or managed setup path so PMS credentials stay outside ChatGPT.
- Paste your Tokeet account ID and API key into the prompted fields.
- Deploy the private connection and open the generated health page.
- Confirm it says Connected to Tokeet 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 Tokeet 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 Tokeet 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 Tokeet'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.
Tokeet issues first, generic OAuth issues second.
Tokeet's Client API needs both the account ID (sent as a query parameter, e.g. ?account=YOUR_ID) and the API key (sent in the Authorization header). Supplying only one fails with a 401 'check your apikey and account id' error.
The Client API is for property-manager accounts; the OAuth ClientID/Secret flow is the separate Partner API, which most single operators do not need.
Most common Tokeet issue: a 401 because the account ID and API key are swapped, or only the API key was supplied without the account query parameter.
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.