# Xano External Collection Bad Request

**URL:** <https://forum.adalo.com/t/xano-external-collection-bad-request/37427>\
**Category:** External Collections, Custom Actions & Collections\
**Created:** [March 23, 2023, 2:50am UTC](https://forum.adalo.com/t/xano-external-collection-bad-request/37427 "2023-03-23T02:50:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesb](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@jamesb](https://forum.adalo.com/u/jamesb)\
**Post date:** [March 23, 2023, 2:50am UTC](https://forum.adalo.com/t/xano-external-collection-bad-request/37427/1 "2023-03-23T02:50:25Z")

</div>

I am using Xano as my external database for my Adalo app. I created an endpoint that takes the user id as an input and returns only that users entries in the table.

- Manually debugging in Xano works successfully
- If I hardcode the user id into the query parameter when setting up the external collection, it works.
- BUT if I use the magic text to pull the user id when setting up the external collection, Adalo sends a bad request to Xano with allllllllllll sort of information in JSON, instead of just the user id.

Anyone else run into this issue?

---

<div class="post-metadata">

**Author:** ![theadaloguy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/theadaloguy/32/8023_2.png) [@theadaloguy](https://forum.adalo.com/u/theadaloguy)\
**Post date:** [March 23, 2023, 4:38am UTC](https://forum.adalo.com/t/xano-external-collection-bad-request/37427/2 "2023-03-23T04:38:18Z")

</div>

Yes I’ve encountered this- seems a bit of an issue. I didn’t solve it but instead just used Auth ID instead as the input. So if it’s a user authenticated (you send the user auth token in the header), you can then use auth-id when building your Xano query.

---

<div class="post-metadata">

**Author:** ![jamesb](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@jamesb](https://forum.adalo.com/u/jamesb)\
**Post date:** [March 24, 2023, 1:44am UTC](https://forum.adalo.com/t/xano-external-collection-bad-request/37427/3 "2023-03-24T01:44:03Z")

</div>

Thanks for the reply!

So I ended up figuring out a workaround: I created an external collection, using the same endpoint and manually configuring it and it works consistently.