# API/Integration swagger functionality

**URL:** https://community.appfarm.io/t/api-integration-swagger-functionality/317
**Category:** Feature requests
**Tags:** service
**Created:** [March 2, 2023, 4:06pm UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317 "2023-03-02T16:06:28Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Sondre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/sondre/32/105_2.png) [@Sondre](https://community.appfarm.io/u/Sondre)
#### Post date: [March 2, 2023, 4:06pm UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317/1 "2023-03-02T16:06:28Z")

</div>

Hey,

After working for a while integrating Appfarm with other systems a feature that stands above all others on the wish list is a more “out of the box” receive/response functionality.

1. An option to receive data using node names in Appfarm  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/1X/8aeda8ba7ca15f57faf723503c43e5bfa7061868.png)

2 An option to make the response data equally structured as the body data connected source/sources.  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/1X/12200de8c9607c82ab4b5dffb3fdf3a09aa6333c.png)

This will address both a source of errors manually writing all attributes and having to explain that the response profile is different than than the post/put profile (if using the built in functionality).  
And maybe even make it 100% responsive with the object classes during development and change?

---

<div class="post-metadata">

### Author: ![kristian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/kristian/32/58_2.png) [@kristian](https://community.appfarm.io/u/kristian)
#### Post date: [March 3, 2023, 11:26am UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317/2 "2023-03-03T11:26:49Z")

</div>

Good input on the first one! Registering a challenge / feature request for that one.

The latter point could need a bit more explaination / an example! 🙂

---

<div class="post-metadata">

### Author: ![Sondre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/sondre/32/105_2.png) [@Sondre](https://community.appfarm.io/u/Sondre)
#### Post date: [March 3, 2023, 1:18pm UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317/3 "2023-03-03T13:18:58Z")

</div>

Say you have a nested data structure in an order - order line structure POST. If I want to communicate that profile structure to another party that is going to send orders to Appfarm, I have to manually write the nested data structure.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/appfarm/original/1X/4d219a310561fb48548fa8e32883d8fffac389bc.png)

Even if the data structure is nested 🙂

---

<div class="post-metadata">

### Author: ![Sondre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/sondre/32/105_2.png) [@Sondre](https://community.appfarm.io/u/Sondre)
#### Post date: [March 3, 2023, 1:20pm UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317/4 "2023-03-03T13:20:15Z")

</div>

This will truly achieve the “just a few clicks” API building 🙂

---

<div class="post-metadata">

### Author: ![Sondre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/sondre/32/105_2.png) [@Sondre](https://community.appfarm.io/u/Sondre)
#### Post date: [March 8, 2023, 7:16am UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317/5 "2023-03-08T07:16:40Z")

</div>

@kristian Is that a good enough explanation? 🙂

---

<div class="post-metadata">

### Author: ![kristian](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/kristian/32/58_2.png) [@kristian](https://community.appfarm.io/u/kristian)
#### Post date: [March 8, 2023, 8:58am UTC](https://community.appfarm.io/t/api-integration-swagger-functionality/317/6 "2023-03-08T08:58:11Z")

</div>

Yes, thanks! Got it 😉 Agree on that one as well, however, it’s takes a bit more to implement. But we have improvements on both building and testing web requests on the roadmap!
