canonical: https://jentic.com/apis/listingsapi.com/listingsapi # Listings API The Listings API manages business locations and keeps their listings in sync across Google, Facebook, Bing, and other publishers. It creates, updates, archives, and searches locations, connects Google and Facebook accounts and matches their listings to locations, flags duplicate listings, and attaches photos. It also pulls reviews, Q&A, and social interactions per location or across many, posts owner responses, reports review analytics and Google, Facebook, and Bing insights, and publishes or schedules social posts to connected Facebook, Instagram, X, LinkedIn, and Pinterest accounts. ## For AI agents Create and update business locations, sync and de-duplicate their listings, respond to reviews, pull Google, Facebook, and Bing insights, and publish social posts. ## Scope Does not run paid search ads, track keyword rankings, or host websites. Use for managing business location listings, reviews, local insights, and social posts only. ## Capabilities - Create a business location and update writable fields such as phone, bizUrl, business hours, and primary Google category - Connect Google and Facebook accounts, trigger listing matches, and confirm which listings belong to which location - List reviews, Q&A, and social interactions for a location or across many, filtered by site, date range, and rating - Post or edit an owner response to a review on its source platform - Read review analytics plus Google, Facebook, and Bing insights for a location over a date range - Publish, schedule, or draft a social post across a brand's connected Facebook, Instagram, X, LinkedIn, and Pinterest accounts - Find duplicate listings for a location and mark them as duplicate or not duplicate ## Use cases ### Agent-run review responses through Jentic A local marketing agent can watch reviews across every location, draft owner replies, and post them back to the source platform. Through Jentic it finds the interactions list and respond operations by intent and loads their schemas, so the developer does not hand-wire the Authorization header or the review filters. Google Reviews accept a single owner reply per review, so the agent edits an existing response instead of posting a second one. Example prompt: List interactions for a locationId with a startDate of 2026-10-01, pick reviews with a low rating that have no response, and post a reply to each with responseContent and its interactionId. ### Multi-location listing sync Brands with many stores keep name, phone, website, hours, and categories consistent across publishers by updating each location once in the Listings API. Only the fields sent in an update are changed, and archive and cancel-archive operations handle closures and reopenings without deleting history. Example prompt: Look up locations by storeCodes 'ATX-01', then update that location's businessHours for Saturday to open 10:00am to 02:00pm. ### Local performance reporting For each location the API returns review analytics KPIs, a review volume and average rating timeline, a per-site breakdown, and Google, Facebook, and Bing insights over a date range, which together form a monthly local search report. Example prompt: Fetch Google insights for a locationId with fromDate 2026-09-01 and toDate 2026-09-30, plus the review analytics overview for the same range, and summarize both. ### Scheduled social publishing Marketing teams publish, schedule, or draft one post for a brand across its connected channels, or queue many posts across brands as one asynchronous bulk job and check each row's result. Post insights and comments come back per connected channel. Example prompt: Create a social post for a socialProfileId on INSTAGRAM and LINKEDIN with action SCHEDULE, scheduleDate 2026-11-14, and scheduleTime 09:30. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/v4/locations` | Create a new location | | POST | `/api/v4/locations/update` | Update a location | | GET | `/api/v4/locations/{locationId}/reviews` | List interactions for a location | | POST | `/api/v4/locations/reviews/respond` | Respond to a review | | GET | `/api/v4/locations/{locationId}/google-analytics` | Google insights for a location | | POST | `/api/v4/social/posts` | Publish or schedule a social post | | GET | `/api/v4/locations/{locationId}/listings/duplicates` | Duplicate listings for a location | | POST | `/api/v4/connected-accounts/trigger-matches` | Match listings to locations | ## Key resources - **Locations** — Business locations with create, update, search, archive, and lookup by store code or id - **Connected accounts and listings** — Google and Facebook account connections, listing matches, and duplicate listing handling - **Interactions** — Reviews, Q&A, and social interactions with responses, settings, and analytics - **Insights** — Google, Facebook, and Bing metrics per location - **Social** — Social profiles, connected channels, single and bulk posts, and post insights - **Photos** — Media attached to a location, with add, remove, and star operations - **Day pass** — Keyless sandbox sign-up and status for trying the API ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 57 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 89 / 100 - Security: 50 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/listingsapi.com/listingsapi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Listings API by hand means choosing between its Authorization header key and the RapidAPI key and host pair, then building nested input objects for each write. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Read operations such as reviews, analytics, and insights put the location id in the URL path (`/api/v4/locations/{locationId}/...`), so a rule can pin those reads to one location. Updates and review responses carry their ids in the request body, so for writes, rules bound which operations your agent may call, not which location; you choose them, so archiving locations or disconnecting accounts is not included unless you add it. - **Credential handling:** Your Listings API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'respond to a Google review' or 'update store hours', and Jentic returns the matching Listings API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **My Business Business Information API** — Google's own API for Business Profile location data - **Google Business Profile Performance API** — Performance metrics for Google Business Profiles - **Buffer API** — Social media scheduling and publishing - **Moz Links API** — Link metrics and domain authority ## FAQ ### What authentication does the Listings API use? Per its OpenAPI spec the Listings API accepts either of two options. Directly, send your key from the developer dashboard in the Authorization header as API followed by the key. Through the RapidAPI proxy, send X-RapidAPI-Key together with X-RapidAPI-Host instead. The four day pass operations, which set up a keyless sandbox, need no authentication. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at request time. ### Is there a Listings API MCP server? You don't need an MCP server to give your agent the Listings API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers location, review, and social operations on demand instead of loading a large tool list into its context. ### Can I respond to Google reviews with the Listings API? Yes. The respond operation posts a public reply to a review or interaction on its source platform, taking responseContent and the interactionId. Google Reviews accept a single owner reply per review, so a second response is rejected; use the edit response operation with the responseId, reviewId, and new responseContent to change an existing reply. ### Is there a free way to try the Listings API? The spec describes a sandbox day pass, when offered, that needs no card. Agents can request one with the day pass signup operation, start it with the emailed code, and poll its status. It covers the locations and listings operations and syncs only to demo directories. ### What are the rate limits for the Listings API? The OpenAPI spec does not specify request rate limits. The social limits operation reports your account's social connection cap and its usage for the current billing period, which is a plan allowance rather than a request limit. See https://listingsapi.com/docs for current limits. ### Can I limit what my agent is allowed to do with the Listings API? Yes. For example, write a rule that allows only the interactions list, review analytics, and Google insights reads under `/api/v4/locations/1800289`/, so the agent can report on that one store while location updates, review responses, and account disconnects stay outside its reach. Every call it makes is logged. ### How do I update a location's hours with the Listings API through Jentic? Search Jentic for 'update business location hours', load the update location operation, and send an input object with the location id and the businessHours you want; only the fields you send change. Jentic injects your key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.