New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Represent upcoming invoices separately from invoices with ids #56
Comments
Thanks for logging! Hmm, the trouble with this endpoint is that it points back to a "standard" invoice API resource, which seems largely desirable, but of course We have a few possibilities to:
I've filed a ticket with the internal team responsible for Stripe's Billing products to see what they want to do. |
When listing invoices, will they always have an This must be true as the pagination |
Yes invoices will always have an id. Only the upcoming invoice endpoint returns a nullable id, and those can't be "listed" or use pagination. |
When using the upcoming invoice endpoint, the response represents an invoice that doesn't exist yet, and does not have an
id
.The openapi spec for Invoice here, however, does not mark
id
asnullable: true
. Which means that code generators will not make it optional, and could fail while parsing.The text was updated successfully, but these errors were encountered: