انتقل إلى المحتوى الرئيسي

Create an organization below the caller scope

POST 

/api/v1/subjects

Requires Idempotency-Key. kind may be omitted from the body; the gateway then reads it as organization, the only kind slice 0 creates. The new subject path is parentPath (default: the caller scope path) plus slug; a parent outside the caller scope is refused.

Two rules on displayName beyond its schema, both because an organization name is published in the trust tree once the organization is admitted. Its letters must come from the scripts this deployment allows (Latin and Arabic unless the operator configured otherwise), and no unbroken run of letters may mix two scripts (a space, hyphen, slash, digit or any punctuation ends a run, so a Latin word joined to an Arabic word by a hyphen is accepted); digits, punctuation and combining marks are always allowed. A name that fails is refused with 400 and code subject.name_script. And it must not read the same as the name of an organization above the new one or beside it, once capitals, character width, invisible characters and spacing are set aside: 409 with code subject.name_taken, whose detail names the path of that organization. Only organizations inside the caller scope are compared, so a 201 is not a promise: the same comparison is made across the whole trust tree when the organization is admitted.

Request​

Responses​

The subject was created.

Response Headers
    X-Correlation-Id

    The correlation id of the request, on every response including 401.