#maximepvrt_api

1 messages ¡ Page 1 of 1 (latest)

prime breachBOT
#

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

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

tranquil tinsel
quaint coral
#

Hey there, can you share an example failing request ID? eg req_123

#

The error message seems to suggest this is restricted on the list requests, but I would not expect a 500 error for that

tranquil tinsel
#

req_2MvBB7lHTtUiwM

#

It seems the API is treating this valid field exactly the same as a non-existent relation. Even when I use the correct path as per the documentation, I get the same 'not expandable' rejection.

# 
"message": "This property cannot be expanded (data.parent.subscription_details.subscriptiondddd).",
quaint coral
#

That's not the same error though:

This property cannot be expanded (data.parent.subscription_details.subscriptiontypo).

vs

Field `data.parent.subscription_details.subscription` cannot be expanded via the invoice list endpoint.

The latter indicating this is not support in the list API specifically

#

For performance reasons, some fields are restricted from expansion on invoice list endpoints, this being one of those fields

tranquil tinsel
#

Thanks !