Skip to main content
Most requests to fal require authentication. You need an API key to call any model on the Model APIs, deploy your own with Serverless, or access any private or shared endpoint. The only exception is endpoints deployed with app_auth = "public", which accept unauthenticated requests. API keys are tied to accounts, not people. If you are working under a team, the key belongs to that team and all members share it. The fal client libraries read your key automatically from the FAL_KEY environment variable, so once it is set, every SDK call and CLI command authenticates without extra configuration.

Create Your API Key

1

Go to the Dashboard

2

Generate a Key

Click Create Key and give it a name you’ll remember
3

Copy Your Key

Copy the key immediately. You will not be able to see it again

Set Your API Key

Set your key as an environment variable:
Or configure it directly in code:
Best practice: Use environment variables instead of hardcoding keys in your code. This keeps your keys secure and makes it easy to use different keys for development and production.

Key Scopes

When creating a key, you’ll choose a scope that controls what the key can access:
If you’re not sure which to choose, start with API scope. You can always create an additional ADMIN key later if you need to deploy models.

Test Your Key

Verify your key works by making a simple API call:
If you see a response with an image URL, your key is working correctly.

Team Keys

If you’re part of a team, make sure to select your team in the top-left corner of the dashboard before creating a key. Keys are scoped to the account (personal or team) that created them.