A clear location identity
Show the business name and address so edits stay attached to the intended location.
Workflow preview · Confirm Google Business access with our team
Bring business locations, opening hours and profile review into your app. Explore a Google Business Profile workflow that keeps every proposed change attached to the right location.
Design a clear profile-management experience, from the selected business to the details under review.
Fans APIPlan your location workspace | Google BusinessConfirm profile access |
|---|---|
Business locationKeep the selected location visible beside every edit. | Business locationConfirm the business profile and the account’s management access. |
Profile detailsReview proposed hours and contact details in context. | Profile detailsUse the fields supported by the relevant Business Profile API. |
Change handlingDistinguish proposed edits from confirmed platform data. | Change handlingCheck request results and applicable platform processing. |
Developer accessKeep permissions and credentials out of the editing interface. | Developer accessBusiness Profile APIs have eligibility requirements and usage limits. |
This is a proposed profile-management workflow. FansAPI Google Business availability is not yet confirmed.
A careful editing flow for information people use to find and visit a business.
Start with the business profile you intend to manage. Keep the name and address visible throughout the flow.
Bring the proposed hours and profile information into one workspace, with a preview of the changes.
Check the location and proposed values together. Use actual API results to track what happens after submission.
Keep the location, proposed hours and final review in one focused experience.
Show the business name and address so edits stay attached to the intended location.
Make the proposed schedule easy to read alongside the rest of the profile.
Keep draft edits separate from the information last confirmed by the platform.
Bring the location and changed fields into one check before submission.
Distinguish submitted changes, errors and platform-confirmed results.
Confirm that the account can manage the location and keep its credentials private.
const response = await fetch(process.env.GOOGLE_BUSINESS_API_URL, {
headers: {
[process.env.GOOGLE_BUSINESS_AUTH_HEADER_NAME]:
process.env.GOOGLE_BUSINESS_AUTH_HEADER_VALUE
}
});
const data = await response.json();
console.log(data);import os
import requests
response = requests.get(
os.environ["GOOGLE_BUSINESS_API_URL"],
headers={
os.environ["GOOGLE_BUSINESS_AUTH_HEADER_NAME"]:
os.environ["GOOGLE_BUSINESS_AUTH_HEADER_VALUE"]
},
timeout=30,
)
print(response.json())<?php
$request = curl_init(getenv('GOOGLE_BUSINESS_API_URL'));
curl_setopt_array($request, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTPHEADER => [
getenv('GOOGLE_BUSINESS_AUTH_HEADER_NAME') . ': ' .
getenv('GOOGLE_BUSINESS_AUTH_HEADER_VALUE'),
],
]);
$response = curl_exec($request);
curl_close($request);
echo $response;require "net/http"
require "json"
uri = URI(ENV.fetch("GOOGLE_BUSINESS_API_URL"))
request = Net::HTTP::Get.new(uri)
request[ENV.fetch("GOOGLE_BUSINESS_AUTH_HEADER_NAME")] =
ENV.fetch("GOOGLE_BUSINESS_AUTH_HEADER_VALUE")
response = Net::HTTP.start(uri.host, uri.port,
use_ssl: uri.scheme == "https", read_timeout: 30
) { |http| http.request(request) }
puts JSON.parse(response.body)var request = HttpRequest.newBuilder()
.uri(URI.create(System.getenv("GOOGLE_BUSINESS_API_URL")))
.header(
System.getenv("GOOGLE_BUSINESS_AUTH_HEADER_NAME"),
System.getenv("GOOGLE_BUSINESS_AUTH_HEADER_VALUE"))
.timeout(Duration.ofSeconds(30))
.GET().build();
var response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());curl --fail-with-body --max-time 30 \
"$GOOGLE_BUSINESS_API_URL" \
-H "$GOOGLE_BUSINESS_AUTH_HEADER_NAME: $GOOGLE_BUSINESS_AUTH_HEADER_VALUE"GOOGLE_BUSINESS_API_URL · server environmentA useful review focuses on the business and the fields being changed.
| Detail | In the workspace | Review focus |
|---|---|---|
| Business | Selected location | The profile your application intends to manage. |
| Address | Location context | Enough detail to distinguish this location from another. |
| Hours | Proposed schedule | The opening hours being prepared for review. |
| Update | Reported outcome | The actual integration result, separate from a local draft. |
The illustration does not update a Google listing or imply a search-ranking outcome.
Prepare the account and permissions your Google Business workflow needs. Confirm the FansAPI connection separately.
Identify the relevant business and location, and confirm the management access held by the account.
Google’s Business Profile APIs have access requirements. Confirm eligibility and the final FansAPI integration separately.
Keep credentials on your server and handle submitted edits, failures and confirmed data as distinct states.
The essentials before your first request.