Authentication

All API requests to genui.sh require authentication using an API key.

Getting Your API Key

API keys are only shown once when created. If you lose your key, you’ll need to generate a new one.

Include your API key in the Authorization header of all requests:

Authorization: Bearer YOUR_API_KEY

curl -X GET https://genui.sh/api/artifacts \
  -H "Authorization: Bearer genui_abc123..."

Use environment variables

Never hardcode API keys in your source code. Use environment variables instead:

export GENUI_API_KEY=genui_your_key_here

Rotate keys regularly

Generate new API keys periodically and revoke old ones from the dashboard.

Use separate keys for different environments

Create separate API keys for development, staging, and production environments.

Monitor usage

Check your dashboard regularly to monitor API usage and detect any anomalies.

If authentication fails, you’ll receive one of these responses:

Status Code	Error	Description
401	`unauthorized`	Missing or invalid API key
403	`forbidden`	API key doesn’t have permission for this resource
429	`rate_limited`	Too many requests, slow down

Example error response:

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid API key provided"
  }
}

API requests are rate limited based on your plan:

Rate limit headers are included in all responses:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1705320000