Create a location from a connected account listing

Creates a new Listings API location by pulling business data from an existing listing in a connected Google Business Profile or Facebook account. The listing must already be present in the account (fetched via POST /connected-accounts/connected-account-listings) and must not already be linked to another Listings API location.

Request shape. The body must be wrapped in an input object with two required fields: connectedAccountId (the account that owns the listing) and connectedAccountListingId (the specific listing to import). There is no listingId field, it is rejected by the schema.

For Google listings the API imports name, address, coordinates, phone, website, description, regular and special hours, primary and additional categories, opening date, store code, and timezone. Payment methods and social profile links are derived from the listing's Google attributes. Photos and videos are not imported, in any role, and Google attributes beyond payment methods and social links are read but not retained. Media on the Google profile is left untouched; import and sync never remove it. To populate media against the new location, upload it separately via POST /api/v4/locations/photos. For Facebook it imports name, location, hours, categories, description, and contact info.

The new location is automatically linked back to the connected account it came from. For a Google import the data is not resubmitted to Google. The profile you imported from is left as it is, and its listing reports syncStatus: IN_PROGRESS until your first POST /api/v4/locations/update publishes to it. Every other publisher is treated normally: order items are generated and the location is submitted to each remaining site enabled on the account.

This endpoint accepts no site scope and no option to disable submissions, so the location is always created against your account's full publisher set. To confine it to a single publisher, set enabledSiteIds on the new location via POST /api/v4/locations/update immediately after creation. Send that update as soon as the location is created: order items for the other publishers are generated shortly after creation, and any that have already been generated are not withdrawn by the update.

Use case: bulk-provisioning locations during onboarding. An agency connects a client's Google account that manages 40 storefronts the agency has never entered into Listings API. Rather than creating each location by hand, list the account's listings and call this endpoint once per connectedAccountListingId to spin up all 40 Listings API locations pre-populated from Google, then bill and manage them normally.

success: true means the location was created and locationId is its database ID. On failure success is false, locationId is null, and errors carries a structured, coded reason, for example { "code": "SY81067", "message": "Invalid connected account listing ID" } when the connectedAccountListingId does not resolve. Other common cases are a listing already connected to another location, or an account whose credentials have expired and must be reconnected via the connect-google or connect-facebook endpoint. To attach a listing to an existing location instead of creating a new one, use the connect-listing endpoint.