# How to create a plugin with backend API calls to populate composer while drafting?

**URL:** https://meta.discourse.org/t/how-to-create-a-plugin-with-backend-api-calls-to-populate-composer-while-drafting/356970
**Category:** Development
**Created:** [March 12, 2025, 2:38pm UTC](https://meta.discourse.org/t/how-to-create-a-plugin-with-backend-api-calls-to-populate-composer-while-drafting/356970 "2025-03-12T14:38:02Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![fabkosta](https://avatars.discourse-cdn.com/v4/letter/f/b3f665/32.png) [@fabkosta](https://meta.discourse.org/u/fabkosta)
#### Post date: [March 14, 2025, 10:24am UTC](https://meta.discourse.org/t/how-to-create-a-plugin-with-backend-api-calls-to-populate-composer-while-drafting/356970/7 "2025-03-14T10:24:43Z")

</div>

Here’s another piece that seems to be pretty important, as it describes how frontend and backend are glued together via routes:

> [@Creating Routes in Discourse and Showing Data](https://meta.discourse.org/t/creating-routes-in-discourse-and-showing-data/48827):
>
> Over time Discourse has grown in complexity and it can be daunting for beginners to understand how data gets all the way from the back end Ruby on Rails application to the Ember.js application in front. This tutorial is meant to show the full lifecycle of a request in Discourse and explain the steps necessary if you want to build a new page with its own URL in our application. URLs First I always prefer to start thinking of features in terms of the URLs to access them. For example let’s say we…

---

_[View the full topic](https://meta.discourse.org/t/how-to-create-a-plugin-with-backend-api-calls-to-populate-composer-while-drafting/356970)._