Create a location

Creates a new business location. On success the location is queued for submission to every publisher in its plan (or, when enabledSiteIds is supplied, just those sites). Required fields: name, a description of at least 200 characters, subCategoryId, countryIso, and, for countries with city-level addressing, city. A location also needs a valid street address and phone before it can actually publish, supply them at create time to avoid a follow-up update.

The returned id is base64-encoded (e.g. TG9jYXRpb246MTgwMDI5MA==); decode it to reveal the internal Location:<databaseId> form. Every subsequent call references this base64 id.

Use case: onboard a single storefront with hours. Send the address, phone, subCategoryId, and a businessHours array, one entry per weekday with type: "OPEN" and { start, end } slots, or type: "CLOSED" with an empty slots array for closed days. Store your own key in storeId so you can later resolve the location via get by store codes without tracking Listings API's ID.

Special hours require regular hours. Special hours (holiday or event overrides, sent as businessHours entries with day: "SPECIAL", type: "OPEN" or "CLOSED", and a specialDate in YYYY-MM-DD form) only publish when the location also carries its regular MONDAY–SUNDAY schedule, Google rejects a location submitted with special hours but no regular hours. Always include the full seven-day businessHours week whenever you set SPECIAL entries; see the update endpoint's hours rules for the full model.

Use case: publishing to a site subset. Pass enabledSiteIds (site IDs from the plan-sites endpoint) to publish the location to a curated subset of directories rather than the full plan, the pattern agencies use to sell tiered site coverage.

Seed Google action buttons at create time. Pass placeActionLinks to set the location's Google action buttons (book an appointment, order online, and so on) in the same call. Valid placeActionType values are APPOINTMENT, ONLINE_APPOINTMENT, DINING_RESERVATION, FOOD_ORDERING, FOOD_DELIVERY, FOOD_TAKEOUT, and SHOP_ONLINE, with at most one preferred link per type. Right after create, each link's name and submissionStatus are null until it syncs to Google. To add, edit, or remove links later, use update a location; see the Place Action Links guide for the full model.

Common errors (returned as 400 with detail in errors[]): description must be at least 200 characters (SY10005), countryIso must be a supported country (SY10036), city is mandatory for countries with city-level addressing (SY10126), state must be a valid ISO code, postal code and phone must be valid for the country, subCategoryId must exist, and storeId must be unique across the account. Every request costs the same against your rate limit regardless of endpoint, so high-volume onboarding trips a 429 on request count alone, honor the Retry-After header and create sequentially rather than in a burst.