Create Project
Project Management
Create Project
Create a new project for the current user
POST
Create Project
Create a new project for your AI-powered application. Projects serve as containers for end users, API keys, and generation requests. Each developer can create multiple projects for different applications or environments.
By Client:
By Product:
Authentication
Requires valid JWT token withdeveloper role.
Headers
Bearer JWT access token obtained from login
Must be set to
developerActive developer key for authentication
Must be
application/jsonRequest Body
Project name (3-100 characters). Should be descriptive and unique among your projects.Examples: “Production API”, “My SaaS App”, “Customer Portal”, “E-Commerce Platform”
Detailed project description (optional, max 500 characters). Describe the project’s purpose, target users, or key features.Example: “AI-powered image generation platform for e-commerce product photography”
Response
Unique UUID identifier for the newly created project
Project name as provided
Project description (null if not provided)
UUID of the developer who created the project (your user ID)
Project status - always
true for newly created projectsISO 8601 timestamp when the project was created
ISO 8601 timestamp of last update (null for new projects)
Example Request
Example Response
Next Steps After Creation
After creating a project, you should:- Generate Project API Keys via Create API Key
- Configure Starter Kit with your project credentials
- Register End Users via Register endpoint
- Monitor Usage via Project Stats
Use Cases
Multi-Environment Setup
Create separate projects for each environment:Multi-Product Portfolio
Manage multiple applications under one developer account:Client Project Management
Create projects for individual clients:Project Limits
Free tier developers can create up to 5 active projects. Upgrade to Cloud Starter or Cloud Premium for unlimited projects.
Tier Limits
| Tier | Max Projects | End Users per Project | API Keys per Project |
|---|---|---|---|
| Free Starter | 5 | 100 | 3 |
| Cloud Starter | 20 | 10,000 | 10 |
| Cloud Premium | Unlimited | Unlimited | Unlimited |
Best Practices
Naming Conventions
✅ Do:- Use descriptive names: “Production - E-Commerce Platform”
- Include environment: “Staging - Mobile App”
- Mention client/product: “Acme Corp - Customer Portal”
- Keep names under 50 characters for display purposes
- Use generic names: “Project 1”, “Test”, “New Project”
- Include sensitive data: API keys, passwords, internal IDs
- Use special characters that break URLs:
#,?,&
Organization Strategies
By Environment:Security Considerations
- Principle of Least Privilege: Create separate projects for different trust levels
- Environment Isolation: Never share API keys between production and development
- Client Separation: Each client should have their own isolated project
- Audit Trail: Use descriptive names and descriptions for tracking
- Regular Cleanup: Deactivate or delete unused projects
Error Responses
Invalid Project Name (422)
Description Too Long (422)
Project Limit Reached (403)
Unauthorized (401)
Insufficient Permissions (403)
Related Pages
List Projects
View all your projects
Update Project
Modify project details
Create API Key
Generate project API keys
Project Stats
Monitor project usage
Cloud Admin Guide
Create via web interface
Quick Start
Complete project setup tutorial

