# Plugin API (Empowering the community)

**URL:** <https://community.penpot.app/t/plugin-api-empowering-the-community/1727>\
**Category:** Feature requests\
**Created:** [October 5, 2022, 5:57pm UTC](https://community.penpot.app/t/plugin-api-empowering-the-community/1727 "2022-10-05T17:57:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucadalli](https://avatars.discourse-cdn.com/v4/letter/l/e495f1/32.png) [@lucadalli](https://community.penpot.app/u/lucadalli)\
**Post date:** [October 5, 2022, 5:57pm UTC](https://community.penpot.app/t/plugin-api-empowering-the-community/1727/1 "2022-10-05T17:57:29Z")

</div>

I understand that the team is currently busy with auto-layout and other highly-requested features. I’m curious where the plugin API falls on the priority list.

I imagine that at this stage the internal API itself is changing so often that having an external-facing API to maintain would be a huge headache. On the flipside, a plugin API would empower the community to build missing functionality and augment the current toolset.

---

<div class="post-metadata">

**Author:** ![carolina.portugal](https://dub1.discourse-cdn.com/flex017/user_avatar/community.penpot.app/carolina.portugal/32/36_2.png) [@carolina.portugal](https://community.penpot.app/u/carolina.portugal)\
**Post date:** [October 6, 2022, 7:57am UTC](https://community.penpot.app/t/plugin-api-empowering-the-community/1727/2 "2022-10-06T07:57:45Z")

</div>

Hi @lucadalli, I have answered this question and other recent FAQ here: [Are you new to the Penpot community? That's how you can get started!](https://community.penpot.app/t/are-you-new-to-the-penpot-community-thats-how-you-can-get-started/1417)

(spoiler: we are still exploring how to do it, but for sure it’s in our plans)