syushchenko_api

[kind ore]

👋 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/1346843103998251078

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[plush monolith]

Hi there 👋 taking a look

Can you help me understand what you're trying to accomplish here?

The tax_breakdown seems to have the breakdown of tax by the type of tax (such as sales tax for a given jurisdiction), whereas line_items.data.amount_tax shows the tax amount for each line item.

[crisp burrow]

Yes, of course, but we would like to understand which tax_breakdown belongs to which row element to get the tax_type and taxability_reason

[plush monolith]

My understanding is there isn't a direct mapping there, as multiple items may be included in the tax amount for a specific tax type and jurisdiction.

[rocky palm]

@plush monolith the case is the following: We want to display in the checkout different tax types, e.g. Sales Tax and Lease Tax for different types of products/services for a given state. Unfortunately there is no reference between the line items and the tax breakdown which, the only one is matching based on array index, whcih is not reliable, since if you have e.g. 2 line items and shipping costs , it results into 3 tax breakdown elements, line item 1 breakdown, shipping breakdown, line item 2 breakdown

[plush monolith]

It doesn't seem like that is supported currently, and I'll file feedback with our teams that this is something you'd be interested in seeing added in the future.

In the meantime, do you get the insight you want if you only include a single line item in each calculation request?

[crisp burrow]

Yes, but for us this is not a solution.

[plush monolith]

Are you able to share a request showing this behavior, so I can include that context in the feature request?

[rocky palm]

@plush monolith we don't have a specific UI visualization of that platform yet

doing individual calls is not a scalable solution and would probably penetrate the Tax Calculation endpoints excessively, since we see order with +90 line items which would result into 90 API calls and some more advanced aggregation logic and error handling on our end

[plush monolith]

I don't need a visualization, I want to see the raw output of our API, so I just need the ID of a request you made to our API where you saw the behavior you're describing.
https://support.stripe.com/questions/finding-the-id-for-an-api-request

[rocky palm]

@crisp burrow please provide the example taxcalc id for the request with sales and lease tax

[crisp burrow]

taxcalc_1QyzfRAKl7vwYuj04QbMSvtD

[plush monolith]

I'll get what I need from that, thanks.

[rocky palm]

Thanks @plush monolith

Thanks @crisp burrow

[plush monolith]

Thanks for taking the time to flag this opportunity for improvement to us, I'll file this feedback with the appropriate team.

[rocky palm]

@plush monolith how will we be informed if this will ever be released?

[plush monolith]

You can subscribe to our developer updates from the bottom of almost all of our documentation pages.