Gemini 3.7 Flash
FastGoogle · Text · Image → Text
Latest fast Gemini model — low-latency multimodal text generation.
gemini-3.7-flashWorkflow: chat-completionsAuthentication
Send your Picsart API key as a bearer token on every request.
Authorization: Bearer <PICSART_API_KEY>Make a request
One endpoint serves every model: POST to /workflows/v1/models/execute with the model id and its input in the body. The nesting is deliberate — the outer paramsis the envelope every workflow takes, and the inner one is this model's own input. Those inner names are the same unified ones the SDK takes, so a call translates one-to-one between the two — no per-vendor naming to learn.
curl -X POST 'https://api.picsart.com/workflows/v1/models/execute' \
-H 'Authorization: Bearer $PICSART_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"params": {
"model": "gemini-3.7-flash",
"params": {
"prompt": "A serene mountain lake at golden hour, ultra detailed"
}
}
}'Parameters
3 parameters, sent inside the inner paramsobject. Identical to the SDK's — one parameter set, whichever transport you use.
| Parameter | Type | Required | Default | Details |
|---|---|---|---|---|
promptPrompt | text | yes | — | — |
imageUrlsImages | file (image[]) | no | — | — |
thinkingThinking | enum | no | off | off, low, medium, high |
Response
The body arrives in the gateway's status envelope, so the output is at response.result — alongside the task id, its status and the credits charged. Asset models return url plus an items array; text models return text instead.
{
"status": "success",
"response": {
"id": "task_abc123",
"status": "COMPLETED",
"result": {
"text": "…generated text…",
"model": "gemini-3.7-flash"
},
"usage": {
"credits": 0
}
}
}