iGMS API
iGMS exposes a JSON API at igms.com/api covering properties, listings, bookings, guests, calendar data, message threads, guest reviews, tasks and direct bookings, authenticated with an OAuth 2.0 access token passed as the access_token query parameter and limited to 1,000 requests per minute.
Written from running this integration in production. Last checked against the iGMS API on 12 November 2026.
iGMS API report card
From iGMS's own documentation. Checked on 12 November 2026.
- Base URL / API style
https://www.igms.com/api, with named methods underv1/andv2/(e.g.v1/bookings,v2/book-property). JSON responses withdataandmeta. source- Auth
- OAuth 2.0 authorization code flow for a registered Developer Program application; the access token is sent as the
access_tokenquery parameter. Token lifetime not documented. source - Rate limits
- Up to 1,000 requests / minute. Exceeding it returns error code 16. source
- Webhooks
- Registered by emailing support@igms.com (client_id, type, URLs). Optional HMAC-SHA256 signature in
X-iGMS-Signaturewith a shared secret. Non-200 answers retried with exponential backoff. source - Read / write coverage
- Read properties, listings, bookings, guests, hosts, calendar data, threads, guest reviews and tasks. Write calendar prices and availability, messages, tasks, door codes, listing status, direct bookings, and accept or decline reservations and alterations. source
- Guest messaging
- Send to a booking’s guest with
v1/message-booking-guest(messaging-sendscope); default channel is the booking’s platform,emailfor direct bookings. Up to 10 images withmessaging-send-attachments. source - Sandbox / test account
- Not documented.
- Partner / marketplace programme
- Developer Program: request access from your iGMS account; most requests approved within 2 to 3 business days; open to all subscription levels. New applications have no scopes until support enables them. source
- Restrictions worth knowing
messaging-sendrequires approval andmessaging-send-attachmentsis granted on request after review. Direct-booking writes need thedirect-bookingsscope. source
What the iGMS API is
iGMS is vacation rental software for hosts who sell on Airbnb, Booking.com, Vrbo and their own direct-booking site, best known for automated guest messaging. Its API lives at https://www.igms.com/api and is a set of named methods rather than a resource tree: v1/bookings, v1/get-calendar-data, v1/get-threads, v1/message-booking-guest, v2/book-property and so on. Responses are JSON with a data array and a meta object for paging.
Every token is tied to an application in the iGMS Developer Program. You request access from your iGMS account, iGMS reviews it, and then you create an application, ask support to enable its scopes and run an OAuth 2.0 authorization code flow to get an access token. The token travels as a query parameter, ?access_token=…, not a header.
Coverage is broad on the read side: properties, listings, bookings, guests, hosts, calendar data, message threads, guest reviews and tasks. Writes are narrower and gated by scope: calendar prices and availability, messages to guests, tasks, door codes, and creating or changing bookings on iGMS’s own direct-booking platform.
Through Repull: iGMS listings, reservations, guests, nightly availability and price, and message threads come back in the same shape as every other connected system. Text replies go out through iGMS, and direct bookings can be created, changed and cancelled with POST /v1/reservations, PATCH /v1/reservations/{id} and POST /v1/reservations/{id}/cancel. iGMS is in beta on Repull.
How to get iGMS API access
- 1.Sign in to iGMS, open the Developer Program page and submit the access request, describing your project. iGMS says most requests are approved within 2 to 3 business days, on any subscription level.
- 2.After approval, click Create an application and enter the App URL (your redirect URI) and a description. A client secret is optional.
- 3.A new application has no scopes. Email iGMS support with your client_id and the scopes you need:
messagingto read listings, bookings, guests and threads,direct-bookingsfor calendar data and direct bookings, andmessaging-sendto reply to guests (granted on approval). - 4.Send the host to
https://igms.com/app/auth.htmlwith your client_id, redirect URI, scopes and a state value. After they allow access, exchange the returned code athttps://igms.com/auth/token(grant_type=authorization_code) for an access token. - 5.Pass the token as
access_tokenon every request, or toPOST /v1/connect/igms/credentialsasaccessTokento connect it to Repull.
iGMS does not document how long an access token lives or a way to refresh it. If a token is revoked, iGMS answers with error code 12 and the host has to authorize the application again.
What will bite you
From running this integration in production and reading the vendor's documentation line by line.
A refused token can come back as HTTP 200
When we tested a bad token, iGMS answered 200 with { "error": { "code": 12, "message": "Incorrect token" } }. Code that checks only the status code treats a dead connection as a working one. Read the body for error.code on every response: 11 is a bad parameter, 12 the token, 13 the application, 14 a missing scope, 15 a method that is temporarily unavailable and 16 too many requests.
No scopes until support turns them on
Creating an application gives you a client_id and nothing else. Every scope is enabled by iGMS support, and messaging-send and messaging-send-attachments are reviewed first. A token issued before a scope was added does not gain it: the host authorizes again.
Webhooks are set up by email
There is no endpoint to register a webhook. You email support@igms.com with your client_id, the webhook type and the URLs. Signing is optional: with a shared secret, iGMS sends X-iGMS-Signature, an HMAC-SHA256 of the timestamp and raw body; without one, requests arrive unsigned. Non-200 answers are retried with exponential backoff.
Only direct bookings can be written
v2/book-property and v2/cancel-booking work on iGMS’s own direct-booking platform (airgms). Airbnb, Booking.com and Vrbo bookings are changed or cancelled on the channel. There is no method that prices a stay, so a booking is created at a total you supply.
Bookings do not carry the guest
A booking has a guest_uid, not a name or email. Guest details come from a separate v1/guests call, and threads from v1/get-threads, whose paging flag is hasNextPage while every other method uses has_next_page.
The token is in the URL
Because access_token is a query parameter, it ends up wherever URLs are logged: proxies, APM tools, error trackers. Scrub it before it lands in your logs.
What it costs to keep working
Getting the first token is the slow part. After that, the work is in scopes, error bodies and polling.
- •Every new capability means another scope request to iGMS support and a fresh authorization from each host.
- •Error handling that reads the body, not the status code, and maps codes 12 to 14 to "ask the host to reconnect".
- •Webhooks registered and changed by email, so most integrations also poll, inside 1,000 requests per minute.
- •Joining guests to bookings yourself, since a booking only names a guest id.
The same job, both ways
iGMS directly
# The token is a query parameter on every call.
curl -s 'https://www.igms.com/api/v1/bookings?access_token=YOUR_TOKEN&page=1'
# A bad token can still return HTTP 200 -- check the body.
# { "error": { "code": 12, "message": "Incorrect token" } }
# Guest names come from a second call.
curl -s 'https://www.igms.com/api/v1/guests?access_token=YOUR_TOKEN&guest_uids=GUEST_UID'Through Repull
# Connect the same access token once.
curl -s -X POST 'https://api.repull.dev/v1/connect/igms/credentials' \
-H 'Authorization: Bearer sk_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"credentials": {"accessToken": "YOUR_IGMS_TOKEN"}}'
# Reservations from iGMS and every other connected system, one shape.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
-H 'Authorization: Bearer sk_live_YOUR_KEY'Why use Repull for iGMS
Your next client may not be on iGMS
If you only ever serve your own iGMS account, call its API directly: the methods are simple once you have a token, and Repull would be a layer you do not need. The cost of doing it yourself arrives with the second system.
Errors you can trust
A token iGMS refuses with HTTP 200 is caught when you connect, and token or scope errors on a write come back as connection_reauth_required rather than as a success.
One reservation shape
iGMS bookings, Hostaway reservations and Guesty’s airbnb2 bookings all come back from GET /v1/reservations in one schema, with platform naming the channel.
Refused writes are refused before anything is sent
A change to an Airbnb or Booking.com booking held in iGMS, or a quote, is answered 422 pms_write_unsupported naming iGMS, and capabilities.pms on the connection says what iGMS can do before you try.
Every system authenticates differently
iGMS is an OAuth token in the query string. Smoobu signs each request, Guesty allows five tokens a day, BookingSync rotates its refresh token on every use. Repull holds each one; you keep one key.
Channels next to the PMS
The same Repull key connects Airbnb, Booking.com and Vrbo directly, and more, alongside iGMS accounts.
Connect iGMS through Repull
Create a key, connect a iGMS account with the credentials iGMS issues, and read reservations in the same shape as every other system you support.
Frequently asked questions
Does iGMS have an API?
Yes. The iGMS API at https://www.igms.com/api covers properties, listings, bookings, guests, calendar data, message threads, guest reviews, tasks and direct bookings. Access goes through the iGMS Developer Program, which is open to every subscription level.
How do I get an iGMS API token?
Request access on the Developer Program page in your iGMS account. Once approved (usually within 2 to 3 business days), create an application, ask iGMS support to enable the scopes you need, then run the OAuth 2.0 authorization code flow: send the user to igms.com/app/auth.html and exchange the returned code at igms.com/auth/token.
What is the iGMS API rate limit?
Up to 1,000 requests per minute. Going over returns error code 16, "Too many requests per minute".
Does iGMS have webhooks?
Yes, but they are registered by emailing support@igms.com with your application’s client_id, the webhook type and your URLs. Add a shared secret to have each request signed with HMAC-SHA256.
Can I send guest messages through the iGMS API?
Yes, with the messaging-send scope, which iGMS grants on approval. Messages go to the booking’s platform by default; images need the separately reviewed messaging-send-attachments scope.
What can Repull do with an iGMS account?
Read listings, reservations, guests, nightly availability and price, and message threads; send text replies; and create, change or cancel iGMS direct bookings at a set total. Calendar and price writes, reviews and listing content are not available through Repull for iGMS. iGMS is in beta on Repull.
The other systems Repull connects
Reference
Auth Type
OAuth 2.0 access token
Required Fields
accessTokenSupported Operations
Connection Guide
Join the iGMS Developer Program from your iGMS account, create an application, ask iGMS support to enable the scopes you need (messaging and direct-bookings, plus messaging-send for replies), then authorize the application on your account to get an access token. Paste it into Repull Connect as accessToken.
Notes
- • One iGMS access token, sent as the access_token query parameter. iGMS issues it through its Developer Program and an OAuth 2.0 authorization code flow
- • iGMS has no self-service webhook registration, so Repull checks iGMS for changes on a schedule
- • Guest replies need iGMS’s messaging-send scope, which iGMS grants on approval
- • Only iGMS’s own direct bookings can be created, changed or cancelled; a price is required because iGMS has no quote
- • Calendar, prices and minimum stay are read, not written, through Repull