#nukesforbreakfast_docs
untold wrenBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1395830396213788684
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rare rune
E.G. I don't want the customer to have to input payments twice if they used link, and have two different sets of stored payment methods, etc. etc.
hexed totem
I'm afraid these are the current limitation for metadata search.
To your questions:
Is there some other way to list invoices by metadata that allows both forward and backwards pagination that I don't see?
Unfortunately no.
If not, is it possible to have 2 customers behave as 1 for the purposes of the end user experience?
I'd recommend maintaining the alarm system information in your own database instead of using Stripe, then search within your own data.
Please also note that Stripe has a rate limit in place: https://docs.stripe.com/rate-limits#rate-limiter
It's possible to hit rate limit if the request loads are high for searching purpose.
rare rune
Yes, alarm system records are maintained in my own database. But, the only relevant field to filter invoices on the list all invoices endpoint is customer. Since it's 1 customer <- N alarm systems <- N invoices, I would have to futher filter the stripe results if I'm querying something like "get me all the invoices chronologically for Alarm System X".
I could store the invoice numbers on the alarm system, but then I'm making however many single get calls, which I figure would be rate limited more quickly than a lower amount of list calls.
Basically, my invoices are on a per alarm system basis. However, 1 customer can own many alarm systems. I don't want to do 1 customer per 1 alarm system because my understanding is Stripe will treat each customer object as separate, meaning things like Link or storing payment methods would be separate for each alarm system, leading to a poor user experience.
hexed totem
Sorry if I'm unclear. What I meant by storing the alarm system records is that the relationships between 1 customer <- N alarm systems <- N invoices should be fully maintained within your database, instead of using Stripe to search for them.
Due to the current limitations on the search and list APIs, alongside with the rate limit considerations, your use case can't be supported now.
rare rune
but I need to pull invoice information from Stripe for display. How would I do that without calling Stripe?
hexed totem
Stripe will send invoice.* events every time when there is a change to the invoice. All those invoice information could be saved within your database for display purpose in the future
rare rune
oh ok I understand what you're suggesting now.
Basically use webhooks to duplicate the info into my database and display it from there.
hexed totem
Yes, that's right!
rare rune
alright, I'll consider that as an option.
hexed totem
Sounds good! Let me know if you have any further question 😄
rare rune
is there a specific rate limit for the list or search endpoints for Invoices?
or is it just the 100 operations per second in prod, 25 per second in nonprod?
hexed totem
There is no specific rate limit for individual endpoints. All endpoints share the same general rate limit, unless explicitly stated otherwise for particular endpoints.
rare rune
ok, and that rate limit applies globally across all requests across all endpoints? E.G. 101 different parallel requests to 101 different endpoints would cause the 100 requests per second limit to be exceeded?
hexed totem
Yes, that's correct
hexed totem
No problem! Happy to help 😄