Represent upcoming invoices separately from invoices with ids about openapi HOT 3 OPEN

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 id is wrong.

We have a few possibilities to:

• Create a separate, duplicate resource for an upcoming invoice.
• Return a symbolic value representing nilable in id.
• Mark id on the standard invoice API resource as nilable.

I've filed a ticket with the internal team responsible for Stripe's Billing products to see what they want to do.

from openapi.

When listing invoices, will they always have an id?

This must be true as the pagination starting_after key takes the id of the last invoice in the array?

from openapi.

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.

from openapi.