The vtex.b2b-organizations-graphql createOrganization and createOrganizationAndCostCentersWithId mutations now accept an optional status argument.

• OrganizationInput and NormalizedOrganizationInput now accept an optional status: String field, with the same canonical values as updateOrganization: active, inactive, and on-hold.
• Omitting status keeps the historical behavior: the organization is created as active.
• Creating an organization with a non-active status does not trigger the organization status-changed email. That email is sent only for status transitions made through updateOrganization.

Previously, an organization could only be created as active. Setting any other status required an immediate follow-up updateOrganization call. This added latency and a failure risk to a common B2B onboarding flow for integrations that must start organizations in a non-active state.

1. No action is required for existing integrations. This change is fully backward compatible.
2. To adopt it, pass status in the input of createOrganization or createOrganizationAndCostCentersWithId.
3. Verify the persisted status with getOrganizationById, not with the mutation response's status field, which reflects the operation result rather than the organization's lifecycle status.

• Organization status on create
• B2B Organizations GraphQL API