Build Growf into your stack.

Overview

The Growf API is organised around REST. It uses predictable, resource-oriented URLs, returns JSON, and relies on standard HTTP verbs and status codes. All requests are made over HTTPS to:

https://api.growf.com/v1

Endpoints and fields may evolve as the product develops; we version breaking changes and announce them ahead of time.

Authentication

Authenticate with a secret API key, generated per workspace under Settings → Developers. Send it as a bearer token on every request. Keep keys server-side, and never expose them in client code.

# Authenticate with a bearer token 
curl https://api.growf.com/v1/clients \ -H "Authorization: Bearer gf_live_sk_..."

Requests & responses

Send request bodies as JSON with a Content-Type: application/json header. Successful responses return a JSON object; collections are returned under a data array with a cursor for pagination.

{ "id": "cl_8f2a", "name": "UBO Agency", "created_at": "2026-05-12T09:24:00Z", "strategies": 12 }

Endpoints

Clients

Briefs & strategy

Agents

Reporting

Example: run the content agent

# Run the content agent against a brief 
curl -X POST https://api.growf.com/v1/agents/content/run 
    \ -H "Authorization: Bearer gf_live_sk_..." 
    \ -H "Content-Type: application/json" 
    \ -d '{ "client_id": "cl_8f2a", "brief_id": "br_19d4", "channel": "social" }'

Errors

Growf uses conventional HTTP status codes. Codes in the 2xx range indicate success, 4xx indicate a problem with the request, and 5xx indicate an error on Growf’s side.

• 400: the request was malformed or missing fields.
• 401: missing or invalid API key.
• 403: the key lacks permission for this resource.
• 404: the resource does not exist.
• 429: too many requests; back off and retry.

Rate limits

The API allows 120 requests per minute per workspace. When you exceed the limit you’ll receive a 429 with a Retry-After header indicating how long to wait. Agent runs are processed asynchronously and don’t count against the per-minute read limit.

Webhooks

Subscribe to events to keep your systems in sync. Register an endpoint under Settings → Developers → Webhooks and Growf will POST a signed payload when something happens.

# Example webhook payload 
{ "event": "agent.run.completed", "run_id": "run_4c71", "client_id": "cl_8f2a", "status": "succeeded" }

Verify the Growf-Signature header against your signing secret before trusting a payload. Need a hand? Reach Support or read the documentation.