Documentation

Authentication

All API requests require authentication using a Bearer token.

Using your API Key

Include your API key in the Authorization header of every request:

Authorization: Bearer ${RENDERFUL_API_KEY}

Developer API keys typically start with sk_ (legacy keys may start with vega_). Agent keys start with rf_.

Example Request

curl -X POST https://api.renderful.ai/api/v1/generations \
  -H "Authorization: Bearer ${RENDERFUL_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"type":"text-to-image","model":"flux-dev","prompt":"A sunset"}'

Security Best Practices

• Never expose your API key in client-side code
• Use environment variables to store your key
• Rotate keys periodically
• Use different keys for development and production

Balance endpoints by key type

Use the balance endpoint that matches the key prefix you are authenticating with.

Key Type	Prefix	Balance Endpoint
Developer API key	sk_ / vega_	GET /api/v1/account/balance
Agent API key	rf_	GET /api/v1/agents/balance

Query developer balance

curl -X GET https://api.renderful.ai/api/v1/account/balance \
  -H "Authorization: Bearer sk_your_api_key"

API Key Format

Renderful API keys follow a specific format for easy identification:

Prefix	Description
sk_	Developer API key for dashboard-created server-side integrations
vega_	Legacy developer API key format still accepted for existing integrations
rf_	Agent API key returned by `POST /api/v1/agents/register`