Projects & Environments
Organise your APIs into projects and environments on apikee.dev.
Projects & Environments
Projects
A project maps to one of your APIs. It has a unique slug (URL-safe identifier) and belongs to your team.
# Create a project with a production environment
curl -X POST "https://apikee.dev/api/v1/project" \
-H "x-api-key: sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"slug": "my-api",
"name": "My API",
"description": "Customer-facing REST API",
"envs": [
{
"type": "production",
"url": "https://api.myapp.com",
"templates": [
{
"name": "Free tier",
"rateLimitDay": 1000,
"rateLimitMonth": 20000
},
{
"name": "Pro tier",
"rateLimitDay": 50000,
"rateLimitMonth": 1000000
}
]
}
]
}'Environments
Each project can have multiple environments (e.g. production, staging, development). The project_env slug is the combination: {project-slug}-{env-type}, e.g. my-api-production.
Project environment slug
The project_env parameter used throughout the SDK and API is constructed as:
{project-slug}-{environment-type}Examples:
my-api-productionpayments-staginginternal-tools-development
Limits per environment
| Resource | Tracked |
|---|---|
| Clients | Count vs max (plan-dependent) |
| Endpoints | Count vs max |
| Rate limit buckets | Per hour / day / week / month |

