# Relationships with Adalo API

**URL:** <https://forum.adalo.com/t/relationships-with-adalo-api/5436>\
**Category:** Get Help\
**Created:** [October 29, 2020, 4:52am UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436 "2020-10-29T04:52:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mephix](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/mephix/32/1983_2.png) [@mephix](https://forum.adalo.com/u/mephix)\
**Post date:** [October 29, 2020, 4:52am UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/1 "2020-10-29T04:52:13Z")

</div>

I’m working with the Adalo API, and its working well, except for one thing. I can’t find a way to set fields of type Relationship. They also don’t appear in the documentation. I can’t find mention in the help or videos of whether they have been deliberately omitted. Am I missing something obvious?

---

<div class="post-metadata">

**Author:** ![Fsteeve](https://avatars.discourse-cdn.com/v4/letter/f/cc9497/32.png) [@Fsteeve](https://forum.adalo.com/u/Fsteeve)\
**Post date:** [October 31, 2020, 5:42pm UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/2 "2020-10-31T17:42:34Z")

</div>

Hi @mephix  
I have the same problem … I agree with you.  
In my case this makes my application unusable …

---

<div class="post-metadata">

**Author:** ![anon78309838](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@anon78309838](https://forum.adalo.com/u/anon78309838)\
**Post date:** [November 2, 2020, 8:53am UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/3 "2020-11-02T08:53:42Z")

</div>

At the moment, this is unsupported as we work towards making improvements to include this within the collections api.

---

<div class="post-metadata">

**Author:** ![AXIOM](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/axiom/32/3515_2.png) [@AXIOM](https://forum.adalo.com/u/AXIOM)\
**Post date:** [November 2, 2020, 9:20am UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/4 "2020-11-02T09:20:33Z")

</div>

There is a workaround for certain situations:

If you have an external source that is based on UUIDs you can always create a list of things and then filter by the related ID. Of course you would have to update these regularly (something like access to the Element ID would really help here 😉 )

---

<div class="post-metadata">

**Author:** ![mephix](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/mephix/32/1983_2.png) [@mephix](https://forum.adalo.com/u/mephix)\
**Post date:** [November 2, 2020, 8:13pm UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/5 "2020-11-02T20:13:48Z")

</div>

Thanks @anon78309838, understood.

---

<div class="post-metadata">

**Author:** ![mephix](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/mephix/32/1983_2.png) [@mephix](https://forum.adalo.com/u/mephix)\
**Post date:** [November 2, 2020, 8:18pm UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/6 "2020-11-02T20:18:44Z")

</div>

thanks @AXIOM, not sure I understand exactly what you are saying, does this work to set a Relationship field?

My use case is that I am creating Dates for people automatically and I want to add the Users to their Dates.

At the moment instead of setting the relationship field, i populate different fields with the user emails (which I use as IDs) that I want to add, then I created a separate “admin” app which displays a button for every email I want to convert to a Relationship. I have to click every button individually. Its hard work and only works for my small userbase, but its the best workaround I have right now.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.adalo.com/system/32/40401_2.png) [@system](https://forum.adalo.com/u/system)\
**Post date:** [November 12, 2020, 8:18pm UTC](https://forum.adalo.com/t/relationships-with-adalo-api/5436/7 "2020-11-12T20:18:49Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
