trmnl/api-docs
0
0
Fork 0
mirror of https://github.com/usetrmnl/api-docs.git synced 2026-04-29 13:42:22 -07:00
Code Issues Packages Projects Releases Wiki Activity

GITBOOK-202: No subject

Browse Source
This commit is contained in:
Ryan Kulp
2026-02-24 01:40:39 +00:00
committed by gitbook-bot
parent 955f674126
commit 8ed5bfa3fb
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugin-marketplace/introduction.md
+4 -6
View File
@@ -4,14 +4,12 @@ description: TRMNL's plugin marketplace lets anyone publish and share their work
# Introduction
Our plugin marketplace is where developers can make plugins for other users to install. Beginning November 2025 [TRMNL pays developers](https://trmnl.com/blog/creator-fund) for their work.
Our plugin marketplace is where developers can make plugins for other users to install. Since November 2025 [TRMNL pays developers](https://trmnl.com/blog/creator-fund) for their work.
There are 2 approaches to publishing a plugin for other users — Public, or Recipe. Review the differences between them before continuing:
There are 2 approaches to publishing plugins for other users — Recipe, or Third Party. Review the differences between them before continuing:
{% embed url="https://help.trmnl.com/en/articles/10546870-compare-custom-plugin-types" %}
**Recipes** may be built inside the TRMNL interface and do not require any 3rd party dependencies, user auth, etc. To build a Recipe, [start here](https://help.trmnl.com/en/articles/9510536-private-plugins). Or browse and install 100s of Recipes here:\
[https://trmnl.com/recipes](https://trmnl.com/recipes)
**Public plugins** require a simplified OAuth2 flow. In this scenario, the plugin author (you) maintains user data and is responsible for data privacy and security. TRMNL fetches markup from your server at regular intervals and generates images for the connected user's device to display. To build a Public Plugin, continue reading this guide. Or browse native + public plugins here: [https://trmnl.com/integrations](https://trmnl.com/integrations)
**Recipes** live inside TRMNL and do not require 3rd party dependencies, user auth, etc. This is our recommended path for plugin development. You can provide [custom form fields](https://help.trmnl.com/en/articles/10513740-custom-plugin-form-builder), monitor [usage analytics](https://trmnl.com/blog/plugin-analytics), and optionally middleman with your own services for even more control. Browse 100s of published Recipes [here](https://trmnl.com/recipes), or start building [here](https://help.trmnl.com/en/articles/9510536-private-plugins).
**Third Party plugins** require a simplified OAuth2 flow with TRMNL. In this scenario, the plugin author (you) maintains user PII and is responsible for data privacy and security. TRMNL fetches markup from your server at regular intervals and generates images for the connected user's device. To build a Third Party plugin, continue reading this guide. Or browse native + third party plugins [here](https://trmnl.com/integrations).