docs(customer): 📝 align POST /customers schema#47
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1973a0b81c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "required": [ | ||
| "tin", | ||
| "phoneNumber" |
There was a problem hiding this comment.
tin optional in CustomerCreate schema
The schema marks tin as required, but the tin field description explicitly says it is optional when the customer entity already exists. This inconsistency causes schema-driven SDKs and request validators to reject a request shape that the documentation says should be valid, blocking the existing-entity creation flow unless users bypass validation.
Useful? React with 👍 / 👎.
| "srtp" | ||
| ] | ||
| }, | ||
| "example": "[srtp]", |
There was a problem hiding this comment.
services example to match array type
services is defined as an array of enum strings, but the example is a single string ("[srtp]") rather than JSON array syntax. This produces an invalid example payload for this schema and can mislead integrators (or fail example validation) into sending the wrong request shape.
Useful? React with 👍 / 👎.
2 participants
No description provided.