feat(customers): require businessInfo when creating a business customer - #716
feat(customers): require businessInfo when creating a business customer#716ls-bolt[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
✱ Stainless preview builds for gridThis PR will update the cli go kotlin openapi php python ruby typescript Edit this comment to update them. They will appear in their respective SDK's changelogs.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…er (#717) ## Summary Makes `businessInfo` a required field when creating a business customer via `POST /customers`. Previously `businessInfo` was optional on `BusinessCustomerCreateRequest`, even though the nested object already requires `legalName`, `taxId`, and `incorporatedOn`. A business customer can't be meaningfully onboarded without it, so this tightens the schema to reject requests that omit it entirely. ## Changes - `openapi/components/schemas/customers/BusinessCustomerCreateRequest.yaml` — add `businessInfo` to the `required` list on the business-specific `allOf` member. This applies only to the `BUSINESS` branch of the create request; individual customers are unaffected. - Regenerated `openapi.yaml` and `mintlify/openapi.yaml` via `make build`. `make lint` passes (only pre-existing, unrelated `schema-properties-*` warnings remain). Note: `info.version` / `servers.url` are unchanged — the spec date-version tracks published API versions, and bumping it implies a new server path, which is a separate coordinated rollout. Requested by @shreyav Original PR: #716

Summary
Makes
businessInfoa required field when creating a business customer viaPOST /customers.Previously
businessInfowas optional onBusinessCustomerCreateRequest, even though the nested object already requireslegalName,taxId, andincorporatedOn. A business customer can't be meaningfully onboarded without it, so this tightens the schema to reject requests that omit it entirely.Changes
openapi/components/schemas/customers/BusinessCustomerCreateRequest.yaml— addbusinessInfoto therequiredlist on the business-specificallOfmember. This applies only to theBUSINESSbranch of the create request; individual customers are unaffected.openapi.yamlandmintlify/openapi.yamlviamake build.make lintpasses (only pre-existing, unrelatedschema-properties-*warnings remain).Note:
info.version/servers.urlare unchanged — the spec date-version tracks published API versions, and bumping it implies a new server path, which is a separate coordinated rollout.Requested by @shreyav