Skip to content

Update OpenAPI spec from ziptax-api#4

Open
Laith-Alayassa wants to merge 1 commit into
mainfrom
openapi-sync/from-ziptax-api
Open

Update OpenAPI spec from ziptax-api#4
Laith-Alayassa wants to merge 1 commit into
mainfrom
openapi-sync/from-ziptax-api

Conversation

@Laith-Alayassa
Copy link
Copy Markdown
Contributor

@Laith-Alayassa Laith-Alayassa commented May 11, 2026

Automated update from ziptax-api@deee6a015c345e903894d9d063e3b94fd01d7180.

Generated by make openapi (which includes x-fern-audiences tagging for Fern docs).

Review notes

  • Check the diff for any unexpected removals or renames.
  • Merging this PR makes the spec available to Fern's sync workflow
    via the raw URL consumed by ziptax-docs.

Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

Open in Devin Review

Comment thread openapi/openapi.json
Comment on lines +2035 to 2095
"responses": {
"200": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/SetMerchantCredentialsResponse"
}
}
},
"description": "OK"
},
"400": {
"content": {
"application/problem+json": {
"schema": {
"$ref": "#/components/schemas/ErrorModel"
}
}
},
"description": "Bad Request"
},
"401": {
"content": {
"application/problem+json": {
"schema": {
"$ref": "#/components/schemas/ErrorModel"
}
}
},
"description": "Unauthorized"
},
"403": {
"content": {
"application/problem+json": {
"schema": {
"$ref": "#/components/schemas/ErrorModel"
}
}
},
"description": "Forbidden"
},
"summary_name": {
"description": "Summary description",
"type": "string"
"422": {
"content": {
"application/problem+json": {
"schema": {
"$ref": "#/components/schemas/ErrorModel"
}
}
},
"description": "Unprocessable Entity"
},
"tax_type": {
"description": "Tax type",
"enum": [
"SALES_TAX",
"USE_TAX"
],
"type": "string"
"500": {
"content": {
"application/problem+json": {
"schema": {
"$ref": "#/components/schemas/ErrorModel"
}
}
},
"description": "Internal Server Error"
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Missing 404 response on /merchant/credentials/set endpoint

The /merchant/credentials/set endpoint accepts a merchantId in its request body to identify which merchant's credentials to set, but its documented responses are missing a 404 Not Found status code. Every other merchant endpoint that operates on an existing merchant by merchantId (/merchant/delete, /merchant/update, /merchant/credentials/get, /merchant/credentials/delete) includes a 404 response for the case where the merchant doesn't exist. This omission means SDK/client code generators will not handle the 404 case for this endpoint, and API documentation will be incomplete.

Prompt for agents
In openapi/openapi.json, the /merchant/credentials/set path's responses object (around line 2035-2095) is missing a 404 Not Found response. Add a 404 response block between the 403 and 422 responses, matching the pattern used by the other merchant endpoints (e.g., /merchant/credentials/get or /merchant/credentials/delete). The block should reference the ErrorModel schema with application/problem+json content type and description 'Not Found'.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants