qstringrequired
Parameter defines the prompt you want to send to Google Gemini.
https://api.sandbase.ai/v1/api/google/gemini-answerGet the answer Google Gemini gives for a question in the Gemini web app, with answer text, cited sources and a token for follow-up questions.
Your output will appear here
Complete the inputs, then click Run.
Get the answer Google Gemini gives for a question in the Gemini web app, with answer text, cited sources and a token for follow-up questions.
curl -X POST "https://api.sandbase.ai/v1/api/google/gemini-answer" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"q": "How does a heat pump work?"}'
The result is returned in outputs[0].data as structured JSON.
| Name | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Parameter defines the prompt you want to send to Google Gemini. |
subsequent_request_token | string | No | Parameter defines the token used to continue a Google Gemini conversation. Pass this token with a new q to send a follow-up prompt that includes the previous prompts and answers as context (multi-turn). The token is returned by the API fr |
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/gemini-answer" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"q": "How does a heat pump work?"
}
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.
qstringrequiredParameter defines the prompt you want to send to Google Gemini.
subsequent_request_tokenstringParameter defines the token used to continue a Google Gemini conversation. Pass this token with a new `q` to send a follow-up prompt that includes the previous prompts and answers as context (multi-turn). The token is returned by the API from your previous request using our Google Gemini API. Gemini keeps a conversation only for a limited time, so the token **expires**: send the follow-up soon after the previous request.
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 Gemini AnswerThis API Google | $0.01 per call | JSON |
Google | $0.01 per call | JSON |
Google | $0.015 per call | JSON |
Google | From $0.002 per call | JSON |
Google | From $0.0015 per call | JSON |
Google | $0.01 per call | JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/google/gemini-answer 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: q (string). Optional: subsequent_request_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 Gemini Answer 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 API access separately.