Sign in
Sub-Organizations

Create a sub-organization.

When creating a user through the API, the verifiedEmail field will automatically be set to true. However, if public signups are used, the email will need to be verified by the user.

post/print-mail/v1/sub_organizations

Request body

namestring required

The name of the user to be created alongside the sub-organization.

emailstring required

The email of the user to be created alongside the sub-organization.

passwordstring required

The password of the user to be created alongside the sub-organization.

phoneNumberstring

The phone number of the user to be created alongside the sub-organization.

organizationNamestring required

The name of the sub-organization.

countryCodestring required

The country code of the sub-organization.

Response

The request has succeeded and a new resource has been created as a result.

Changes

Changed in 1 of the 7 revisions of this API.44

  • c8fedcbd705e44See the full diff
    • ●

      added the new internal_server_error enum value to the error/type response property for the response status 500

      response-property-enum-value-added

    • ●

      added the new not_found_error enum value to the error/type response property for the response status 404

      response-property-enum-value-added

    • ●

      added the new rate_limit_exceeded_error enum value to the error/type response property for the response status 429

      response-property-enum-value-added

    • ●

      added the new validation_error enum value to the error/type response property for the response status 400

      response-property-enum-value-added

    • ○

      added subschema #1 subschema #2 to the response body anyOf list for the response status 401

      response-body-any-of-added

    • ○

      added subschema #1 subschema #2 to the response body anyOf list for the response status 403

      response-body-any-of-added

    • ○

      removed subschema #1 subschema #2 from the response body anyOf list for the response status 401

      response-body-any-of-removed

    • ○

      removed subschema #1 subschema #2 from the response body anyOf list for the response status 403

      response-body-any-of-removed

    This revision also has 21 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog