ListingsAPI integration

Build a working integration around the user's language, existing application, and intended publisher workflow. The REST base URL is https://listingsapi.com/api/v4. The hosted MCP endpoint is https://listingsapi.com/mcp.

Choose the path from the request

Infer whether the user is adding to an existing app, building a new one, or onboarding a ListingsAPI account. Inspect an available codebase to learn its language, HTTP client, configuration, job queue, and testing conventions. Reuse them. Ask for missing decisions only when they affect the next step; do not repeat questions the user already answered.

For a new app, establish the language/framework and whether it serves one ListingsAPI account or multiple customer accounts. For account onboarding without a new app, use existing MCP tools where available and provide a small REST or SDK example only when it helps. Do not scaffold an application merely to connect a publisher.

Read the first-location walkthrough for authentication, location creation, publisher linking, and submission checks. It builds on the client scaffold, which supplies Python and TypeScript examples. These are examples to adapt and validate, not a reason to replace the application's existing libraries.

Authenticate and make one read

• REST requests use Authorization: API <key>. MCP client OAuth bearer tokens do not authenticate REST. Prefer the existing MCP client's OAuth flow when that is the chosen integration route.
• Keep API keys server-side in an environment variable such as LISTINGSAPI_KEY or the app's secret store. Never request a secret in chat, commit it, return it to a browser, or log the authorization header.
• Use a Read key for reads. Location writes and publisher connections need Write access. Creating credentials or granting OAuth access requires the user's authorization; a skill installation does neither.
• For multiple customers, store each customer's key encrypted and bind every request/job to the correct tenant. Never reuse one tenant's cached client for another.
• Read a small location page first and handle an empty account as a valid result. Only run an authenticated read when access to that account is authorized. A Day Pass covers sandbox locations/listings, not reviews, posts, analytics, or connected publishers.