What the service list workflow manages
This workflow handles structured services that appear on eligible Google Business Profile locations. It is useful for salons, clinics, agencies, repair shops, local service businesses, and other categories where Google allows service list editing.
Endpoint and payload shape
Use GET /api/v1/misc/google-business/location/service-list to read the current service list and PATCH /api/v1/misc/google-business/location/service-list to update it. PATCH requires teamId, fields with serviceItems, and a serviceItems array that follows the shape Google accepts for that location.
Eligibility matters
Not every business category can modify service lists. Before showing a service editor, read metadata from GET /api/v1/misc/google-business/location and check canModifyServiceList. If it is not available, your product should explain that the location is not eligible instead of showing a broken editor.
Where teams usually get stuck
The object shape can vary by Google category and setup. Building serviceItems entirely from scratch is where teams usually step on a rake. The safer workflow is GET current service list, edit those objects in your app, then PATCH the adjusted serviceItems array back.
How bundle.social fits
bundle.social keeps service list operations in the same Google Business Profile management surface as location fields, hours, attributes, food menus, media, posts, and reviews. That is cleaner than running one integration for posting and another hidden integration for services.