data_idstringrequired
Parameter defines the Google Maps data ID. Find the data ID of a place using our Google Maps API.
https://api.sandbase.ai/v1/api/google-maps/postsGet the owner posts and updates published on a Google Maps place by data ID, with text, images, date and links.
Your output will appear here
Complete the inputs, then click Run.
Get the owner posts and updates published on a Google Maps place by data ID, with text, images, date and links.
curl -X POST "https://api.sandbase.ai/v1/api/google-maps/posts" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"data_id": "0x89c259a61c75684f:0x79d31adb123348d2"}'
The result is returned in outputs[0].data as structured JSON.
| Name | Type | Required | Description |
|---|---|---|---|
data_id | string | Yes | Parameter defines the Google Maps data ID. Find the data ID of a place using our Google Maps API. |
next_page_token | string | No | Parameter defines the next page token. It is used for retrieving the next page results. 10 results are returned per page. |
json_restrictor | string | No | Parameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details. |
$0.010 per successful call. Failed calls are not charged.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/google-maps/posts" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"data_id": "0x89c259a61c75684f:0x79d31adb123348d2"
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
data_idstringrequiredParameter defines the Google Maps data ID. Find the data ID of a place using our Google Maps API.
next_page_tokenstringParameter defines the next page token. It is used for retrieving the next page results. `10` results are returned per page.
json_restrictorstringParameter defines the fields you want to include in the output, reducing payload size for faster response. See the JSON Restrictor documentation for more details.
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Google Maps PostsThis API Google Maps | $0.01 per call | JSON |
Google Maps | $0.01 per call | JSON |
Google Maps | $0.00015 per call | Async JSON |
Google Maps | $0.01 per call | JSON |
Google Maps | $0.00015 per call | JSON |
Google Maps | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/google-maps/posts with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
$0.01 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: data_id (string). Optional: next_page_token (string) and json_restrictor (string). The Parameters table and the Playground on this page list every field.
A JSON response returned in the same HTTP request (synchronous).
No. Google Maps Posts runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Google Maps API access separately.