ShowMojo Legacy API
The legacy version of the ShowMojo API provides programmatic access to core platform features. It enables clients to synchronize property listings, manage availability, and perform basic data integration with external systems.
This version of the API supports listing import, export of structured reports, lead creation, and tour scheduling. It is intended for systems that require direct synchronization with ShowMojo.
The legacy API is the current, supported API and is the one to build against. Version 4 is under development and not yet available for integration; it will be announced in the changelog when it is ready.
Changes to the API and to this documentation are listed, with dates, in the API changelog. Breaking changes follow the versioning and deprecation policy.
Request tracing
Every response, including errors, carries an X-Request-Id header with a unique id for that request. Log it with your requests and quote it when you contact support, so the request can be found in ShowMojo's logs.
ShowMojo generates a UUID when the request has no X-Request-Id header. If you send one, it is echoed back in the response, which lets you correlate calls with your own trace ids. The value may contain letters, digits, -, _ and @; other characters are stripped and the id is cut to 255 characters.
HTTP/1.1 200 OK
X-Request-Id: 2f1c3b6e-5d4a-4f0e-9c3b-7a8d9e0f1a2b
Authentication
- HTTP: Bearer Auth
- HTTP: Basic Auth
- API Key: tokenAuth
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Bearer format: | JWT |
Deprecated, sunset 2027-01-19. ShowMojo login and password sent as HTTP Basic auth. Announced 2026-10-16; requests using it receive 401 Unauthorized from the sunset date. Switch to the account API token: replace the Authorization: Basic ... header with Authorization: Token {token}, using the token from Settings > Listing Import. No other change is needed; every endpoint that accepted Basic auth accepts the token. See the versioning and deprecation policy.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | basic |
Account API token, generated self-serve in Settings > Listing Import and sent as Authorization: Token {token}.
Each account has one active token. Generating a new one revokes the previous one immediately: requests that still send the old token receive 401 Unauthorized. There is no separate revoke action; to revoke a token, generate a new one.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | Authorization |