Skip to main content
A project is the security boundary for AvraAPI credentials, provider access, and UPG runtime behavior.

Project environments

Each credential is linked to one project environment. The API resolves the credential and selected environment together. A Development credential cannot authenticate a Production request by changing X-ENV.

Project ownership

The user who creates a project is its technical owner. That owner retains core control even if the project is later connected to a Business Workspace for approved management work.

Technical Owner

The AvraAPI user who originally created the project.

Parent Workspace

The Personal or Business Workspace the project belongs to.

UPG Attachment

An optional active UPG project slot for payments.

Pause and resume

Pausing a project blocks API use for that project. Treat project_paused as a non-retryable state until an authorized project owner or manager resumes the project.

Connect a project to a Workspace

Workspace connection does not share a user account or reveal API secrets. It uses a time-limited Connect Key with explicit delegated permissions. Review Project linking before connecting a client project.
For UPG, a project needs both an active gateway configuration and an active UPG project slot. A project’s ordinary parent Workspace alone does not enable payment checkout.
Last modified on October 1, 2026