diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png deleted file mode 100644 index 4b67b97..0000000 Binary files a/.gitbook/assets/image (1).png and /dev/null differ diff --git a/.gitbook/assets/plugin-installation-flow.svg b/.gitbook/assets/plugin-installation-flow.svg new file mode 100644 index 0000000..de3c225 --- /dev/null +++ b/.gitbook/assets/plugin-installation-flow.svg @@ -0,0 +1,79 @@ + + Plugin Installation Flow + Flow diagram between TRMNL and Your Web server showing five installation steps. + + + + + + Plugin Installation Flow + Plugin Installation Flow + + + + + + + + + TRMNL + TRMNL + Your Web server + Your Web server + + + + + + + 1. Installation Request + 1. Installation Request + + + + + + + 2. Fetch access_token + 2. Fetch access_token + + + + + + + 3. return access_token + 3. return access_token + + + + + + + 4. Installation Callback + 4. Installation Callback + + + + + + + 5. Success Webhook + 5. Success Webhook + diff --git a/plugin-marketplace/plugin-installation-flow.md b/plugin-marketplace/plugin-installation-flow.md index ca53865..560d13b 100644 --- a/plugin-marketplace/plugin-installation-flow.md +++ b/plugin-marketplace/plugin-installation-flow.md @@ -4,7 +4,7 @@ description: OAuth installation flow between TRMNL and your web server. # Plugin Installation Flow -
+
Plugin installation flow between TRMNL and your web server
Third Party plugins use a simplified OAuth2 flow. There is no `client_id` or `client_secret` to manage — TRMNL identifies your plugin by the URLs you registered during [Plugin Creation](plugin-creation.md), and each installation is authorized by a single-use `code`.