TeamGrid API v1 is cell-aware. Official clients derive the regional endpoint from the credential and the destination cell performs the authoritative authentication.
| Region | Endpoint | Current availability |
|---|---|---|
| Germany | https://api.de.teamgrid.app/v1 |
Stable |
| United States | https://api.us.teamgrid.app/v1 |
Stable |
The global v0 hosts are not API v1 endpoints during the controlled rollout:
https://api.teamgrid.app
https://api.teamgridapp.comRouting requirements
- Do not rewrite a regional v1 URL to a global v0 hostname.
- Do not follow a bearer redirect across regions.
- Do not infer authorization from the region and cell hint in the token prefix.
- Let the SDK or CLI derive the endpoint unless you are implementing a direct HTTP client.
- Use a base URL override only for a controlled staging or loopback environment.
Business data, credential hashes, audit records, and write delivery stay in the owning cell. The global edge does not persist bearer credentials or request payloads.
For endpoints that expose resource revisions and strong ETags, those validators are also cell-local. Return them only to the same credential’s regional endpoint. A tag is not proof of authorization, is not portable to another workspace or cell, and must never be used to justify following a bearer redirect. Stable projects, project sharing, tasks, and project templates expose these validators on their qualified reads and mutations.