Create a project_

Create an Appwrite project for a customer with the Organization API and a Partners key.

2 min read

Projects belong to an organization, so the Organization service creates them. A platform that gives every customer their own project calls this once per customer, then configures the new project with the pages in the rest of this section.

Partners key required

Creating a project needs a Partners key with the projects.write scope, not a project API key. A project API key is scoped to one project and cannot create another. Pass the organization ID with the key and send no project ID.

Create a project

Pass a project ID, a display name, and the region the project's data lives in. Store the returned ID against your own customer record.

Regions

The region fixes where the project's data lives and which regional endpoint its SDK calls use. It cannot be changed after creation, so pick it from the customer's own requirements. See Regions for the full list.

Retries

ID.unique() returns a new ID on every call, so a retried create makes a second project. To keep provisioning safe to retry, derive the project ID from your own customer ID and pass that instead, or record the returned ID before the provisioning step returns.

Next steps

Once the project exists, switch to a project API key to configure it. Create that key in the Console, then work through the configuration pages:

API keys

Create and manage the keys your backend uses inside the project.

Provisioning

Apply a standard baseline to a new customer's project from a script.

Was this page helpful?

Share what worked or what we should fix. Once approved, our agents automatically apply suggested updates to the docs.