listingsapi-multi-location-posting
ListingsAPI multi-location posting
Prepare a campaign with explicit locations, publishers, copy, media, and timing. Publish only the concrete campaign the user approves.
Preflight the campaign
Use an existing MCP connection to https://listingsapi.com/mcp or an existing REST integration at https://listingsapi.com/api/v4. MCP accepts its client OAuth flow or Authorization: API <key>; REST uses the API header. Keep credentials in the existing secret store or environment. Publishing needs write access. Day Pass excludes posts.
Resolve the requested locations with locations_search/locations_all and retain returned Relay IDs. Read all pages needed for a region, tag, or account-wide target. Do not treat a first page as the entire campaign audience. If a cursor repeats, a page is missing, or access fails, label the target list incomplete and resolve it before publication.
For every intended location/publisher pair, check listings_premium and, where needed, connected_accounts_list. Google and Facebook profiles must be connected and matched. A connected account without a matching location is insufficient. Report blocked targets; changing the approved target set requires approval, including sending only to the ready subset.
Confirm the post type, per-site message, CTA and destination, media URL, and any event or offer terms. Media must be user-approved and publicly retrievable by the publisher; do not upload or make private assets public implicitly. For scheduling, resolve timezone and exact start/end instants. Offer validity dates are distinct from the post's publication window. Use current event/offer schemas rather than guessing fields.