# Best practices for using Collections vs Requests+variable?

**URL:** <https://community.weweb.io/t/best-practices-for-using-collections-vs-requests-variable/4028>\
**Category:** How do I?\
**Created:** [August 25, 2023, 5:33pm UTC](https://community.weweb.io/t/best-practices-for-using-collections-vs-requests-variable/4028 "2023-08-25T17:33:33Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![felipegranado](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/felipegranado/32/6306_2.png) [@felipegranado](https://community.weweb.io/u/felipegranado)\
**Post date:** [March 19, 2024, 1:03pm UTC](https://community.weweb.io/t/best-practices-for-using-collections-vs-requests-variable/4028/12 "2024-03-19T13:03:32Z")

</div>

Hi @elyseholladay !

If I understand your question, I also went through this recently.

Generally, those who came from Bubble have a little difficulty, because when we create an API call, we define whether it is an action call or a data call. In WeWeb/Xano there is no such distinction and “everything is exposed” to us.

Currently I have to create all GET calls in Collections and POST and PATCH calls as a workflow, creating the parameters and linking them with the necessary parameters of the call.

I don’t know if this was the topic of the question, but I thought it would be interesting to share this vision.

Best Regards,

---

_[View the full topic](https://community.weweb.io/t/best-practices-for-using-collections-vs-requests-variable/4028)._