# Does the API support AWS Presigned URLs?

**URL:** <https://community.perplexity.ai/t/does-the-api-support-aws-presigned-urls/3470>\
**Category:** General\
**Created:** [January 11, 2026, 5:11pm UTC](https://community.perplexity.ai/t/does-the-api-support-aws-presigned-urls/3470 "2026-01-11T17:11:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![user62](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/user62/32/2367_2.png) [@user62](https://community.perplexity.ai/u/user62)\
**Post date:** [January 11, 2026, 5:11pm UTC](https://community.perplexity.ai/t/does-the-api-support-aws-presigned-urls/3470/1 "2026-01-11T17:11:03Z")

</div>

Hi, I’ve noticed that standard public image URLs work perfectly with sonar models, but AWS Presigned URLs consistently result in a 400 error.Could you confirm if this is a known limitation regarding URLs with query parameters? If Presigned URLs are not supported, is sending images as Base64 encoded strings the only recommended workaround at the moment?

---

<div class="post-metadata">

**Author:** ![Neel\_Buddhdev](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/neel_buddhdev/32/2402_2.png) [@Neel\_Buddhdev](https://community.perplexity.ai/u/Neel_Buddhdev)\
**Post date:** [January 12, 2026, 5:36am UTC](https://community.perplexity.ai/t/does-the-api-support-aws-presigned-urls/3470/2 "2026-01-12T05:36:26Z")

</div>

same query, same for azure too.