#UseDigest
eager citrus
vague wyvern
Hello 👋
These fields are "expandable"
https://stripe.com/docs/api/accounts/object#account_object-settings-branding-icon
You can expand them in order to look at the full object
which should list the URL
plush lynx
In the docs, even after expanding it, the URLS are not public... it gives me a files.stripe.com URL which requires login. Do you guys not provide a public URL to the icon or logo?
rocky moth
Can you tell me more about what you are trying to do? I think that is the only URL we give, I don't think we provide a public URL like that but can look in to it
plush lynx
When a user completes oauth flow and is redirected back to our app, we want to display their stripe icon/logo on our side so they know which account is connected.
This is for a new stripe account, I looked at the docs for an old stripe account and the logo field has an S3 URL... so maybe you guys stopped providing public URLs on new accounts
rocky moth
Gotcha, checking in to this and will get back to you
What doc are you looking at specifically?
plush lynx
This one: https://stripe.com/docs/api/accounts/object
For the stripe account I'm currently signed into, an s3 url is provided.
For a different brand new stripe account as of like 2 weeks ago, just a file path is given for the icon
rocky moth
Can you send me the IDs of these two accounts (acct_1234)?
plush lynx
acct_1NNLpkIJi7H28wNk
and
acct_17ar9zBvGmp7mni2
rocky moth
Thank you
Having trouble finding further info. I will reach out to my colleagues and get back to you with what we can find
plush lynx
thanks
vague wyvern
Hello again 👋
Have you tried creating a file link?
https://stripe.com/docs/file-upload#download-file-contents:~:text=If you want unauthenticated
plush lynx
Have not, was hoping there was just a public URL for icon/logo we could use without going through additional steps. Was confused since older accounts appear to have an S3 url on them, but new ones dont.
vague wyvern
Yeah we probably changed something, not sure what though as the changelog doesn't call it out explicitly. I can look into it but it might take a while.
Just want to make sure creating a file link works as a workaround
Ah found it
FileUpload objects have been renamed to File objects. Additionally, the url attribute now contains an authenticated URL (i.e. you will need to use your secret API key to download the file’s contents.) You can create a file link to obtain a publicly-accessible URL for the file.
that's probably when the switch to file IDs happened too
It's the difference in API version on the accounts