Create an organization; the caller is its first owner
The login follows the namespace rule (Login): one space with
people's logins, so a taken name (a person's or an org's) is 409
namespace_taken and a reserved one 400 reserved_name. The
namespace, the org and the caller's owner row are written in one
batch, so of two creates of one name at once, one wins.
https://app.gitpando.com/v1/orgsAuthorisation
Request bodyJSONrequired
- loginstringrequired
A user's login, which is their namespace, or an organization's (one space for both): 1 to 39 lower-case letters, digits and single hyphens, no hyphen at either end (input in any case is lowered). Reserved, because a namespace is the first URL segment: v1, healthz, login, logout, settings, assets, fonts, new, api, app, static, orgs, users, docs, install. A login made at sign-in comes from the email's local part, skipping reserved and taken names (
base,base-2, ...base-999, then a random tail).pattern: ^[a-z0-9](?:[a-z0-9]|-(?=[a-z0-9])){0,38}$
Returns
201
Created
- loginstringrequired
A user's login, which is their namespace, or an organization's (one space for both): 1 to 39 lower-case letters, digits and single hyphens, no hyphen at either end (input in any case is lowered). Reserved, because a namespace is the first URL segment: v1, healthz, login, logout, settings, assets, fonts, new, api, app, static, orgs, users, docs, install. A login made at sign-in comes from the email's local part, skipping reserved and taken names (
base,base-2, ...base-999, then a random tail).pattern: ^[a-z0-9](?:[a-z0-9]|-(?=[a-z0-9])){0,38}$