#ebllg
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- ebllg, 3 days ago, 12 messages
I am just wondering whether there has been a recent change in the implementation of /v1/invoices/upcoming/lines endpoint
no I don't think so, you can see all API changes listed here: https://stripe.com/docs/upgrades
Can you tell me when this field is null and when it is not in the response of /v1/invoices/upcoming/lines
https://stripe.com/docs/api/invoices/line_item#invoice_line_item_object-invoice
I am wondering, under what circumstances I will see a non-null value in the invoice field for an invoice item that is returned in the response of /v1/invoices/upcoming/lines
maybe your account has some special feature
can you share the raw JSON you're seeing?
and/or the request ID req_xxx of the call to the API you're making
invoice id I see it in invoice field of line items is in_1OjM0GIQk419OSQPPrTw0ots
i am calling this endpoint from stripe's test shell
ok
can you give me an ID of any object on your account? Like the cus_xxx Customer ID you're using, anything
cus_PYS169X6TxSsv0
to clarify, what is "stripe's test shell"?
the shell that can be opened from bottom right corner in the dashboard when you are on test mode
ah that thing
anyway I'm not entirely sure what causes this, you are using a 2017 API version and it's possible it used to return an ID for this.
It's also likely that this is a bug in the Shell and it's returning fields/behaviours that are not meant to be in the public API(I think it's that to be honest)
if you make a regular API call using your own code or stripe-cli installed locally does it return an ID?
yes, it is not specific to the shell
i made a call with node sdk and still got the invoice id
strange
"anyway I'm not entirely sure what causes this, you are using a 2017 API version and it's possible it used to return an ID for this."
It wasn't returning until very recently though. We started having this issue today.
so you are saying, ID shouldn't be returned, right?
AFAIK it's not supposed to be but I'm not 100% sure
how can we investigate this more, should i contact support via email?
definitely could be a bug or unintentional change
if you have like raw JSON response + request ID req_xxx of identical requests where one didn't have the ID and one did, opening a support ticket with that would be ideal yes
ok, thank you
I can find some internal discussion of this so I do think something changed, I'll raise it too
in any case we can add new fields to existing resources, that is backwards-compatible . I think that is what happened here
this is an existing field though, it is not something newly added. it was coming null until recently, now it is filled with an id that doesn't point to an existing invoice.
yeah maybe
sorry without seeing the raw JSON that I asked for initially I'm still a bit confused on the exact field we're looking at
anyway I've followed up internally and I'd suggest opening a support ticket and we'll get it figured out
I tried it on my account at least and I still see invoice:null on lines.data[0].invoice when calling the Upcoming Invoice API for instance, but it's possible there's some kind of phased rollout
it would really help me drive this internally if you could share the exact raw JSON API response you're getting from a specific API call, since I can't repro this on my end
does this request ID help: req_UWPMreuA6jVhOq
no since we don't store the GET response
hence why I need you to share the raw response you see with me
this endpoint is always a pain to debug for team unfortunately 🙂
I see, let me check
object: 'list',
data: [
{
id: 'ii_1OjL7bIQk419OSQPVuz8UcyB',
object: 'line_item',
amount: 9600,
amount_excluding_tax: 9600,
currency: 'usd',
description: '1 seat added',
discount_amounts: [],
discountable: true,
discounts: [],
invoice: 'in_1OjMJ9IQk419OSQPCo9Tk8MC',
invoice_item: 'ii_1OjL7bIQk419OSQPVuz8UcyB',
livemode: false,
metadata: {},
period: [Object],
plan: null,
price: [Object],
proration: false,
proration_details: [Object],
quantity: 1,
subscription: null,
tax_amounts: [Array],
tax_rates: [],
type: 'invoiceitem',
unique_id: 'il_tmp_1OjL7bIQk419OSQPVuz8UcyB',
unit_amount_excluding_tax: '9600'
},
{
id: 'sub_1OjL7GIQk419OSQPsiiMx45N',
object: 'line_item',
amount: 38400,
amount_excluding_tax: 38400,
currency: 'usd',
description: null,
discount_amounts: [],
discountable: true,
discounts: [],
invoice: 'in_1OjMJ9IQk419OSQPCo9Tk8MC',
livemode: false,
metadata: [Object],
period: [Object],
plan: [Object],
price: [Object],
proration: false,
proration_details: [Object],
quantity: 38400,
subscription: null,
subscription_item: 'si_PYS1fuXeeInzFc',
tax_amounts: [Array],
tax_rates: [],
type: 'subscription',
unique_id: 'il_tmp_1b30cdIQk419OSQP4cdc312a',
unique_line_item_id: 'sli_1b30cdIQk419OSQP4cdc312a',
unit_amount_excluding_tax: '1'
}
],
has_more: false,
url: '/v1/invoices/upcoming/lines?customer=cus_PYS169X6TxSsv0'
}```
ok perfect thanks
and to be crystal clear, do you only see this when using Stripe Shell in the Dashboard?
no, i am also getting this when i use node sdk
in fact, this is the response i get when i send a request with the sdk
ok I got it now
it only happens when explicitly calling /v1/invoices/upcoming/lines and I can repro that way too
it's not returned when calling /v1/invoices/upcoming and looking in lines of that Invoice
I think that's an oversight on our part so I'll work with that internally.
But yeah AFAIK this ID is supposed to be null, it's an oversight in this case
thanks for the report!
thank you too! so in that case i guess we should use /v1/invoices/upcoming
that's one option yes
btw how can we get notified once this issue is resolved