# OpenAPI documentation of SurveySparrow API

**URL:** <https://community.surveysparrow.com/t/openapi-documentation-of-surveysparrow-api/3809>\
**Category:** Feature Requests & Ideas\
**Created:** [July 17, 2024, 3:13am UTC](https://community.surveysparrow.com/t/openapi-documentation-of-surveysparrow-api/3809 "2024-07-17T03:13:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OrgAcuity2](https://avatars.discourse-cdn.com/v4/letter/o/90db22/32.png) [@OrgAcuity2](https://community.surveysparrow.com/u/OrgAcuity2)\
**Post date:** [July 17, 2024, 3:13am UTC](https://community.surveysparrow.com/t/openapi-documentation-of-surveysparrow-api/3809/1 "2024-07-17T03:13:10Z")

</div>

My company's application heavily uses [SurveySparrow's REST API](https://developers.surveysparrow.com/rest-apis) for automation of survey builds. Is there any plan to create request and response model documentation that adheres to the OpenAPI specification? This would make the development and testing process for a lot of software that's dependent on SurveySparrow a lot easier and less error prone.

---

<div class="post-metadata">

**Author:** ![SurveySparrow\_Support](https://dub1.discourse-cdn.com/flex013/user_avatar/community.surveysparrow.com/surveysparrow_support/32/322_2.png) [@SurveySparrow\_Support](https://community.surveysparrow.com/u/SurveySparrow_Support)\
**Post date:** [July 17, 2024, 2:27pm UTC](https://community.surveysparrow.com/t/openapi-documentation-of-surveysparrow-api/3809/2 "2024-07-17T14:27:57Z")

</div>

Hello there,

Welcome to the community! 😀

We have Swagger documentation with a sample payload response. Simply add "/documentation" to your Account Domain URL.

Enjoy exploring!