garj
Hi,
My phoenix app currently supports server side rendering. I would like it to support json end point as well. I know I can easily do this in router.ex by adding a scope: “/api/” and pipe_through api plug. However I do not know if I should create seperate controllers for the json app or I should modify existing controllers and render different view depending on the request. Any convention or thoughts related to this? Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hubertlepicki
From my experience, the same controllers returning JSON view only works when the app is really simple CRUD-type of thing.
The needs of API client (either JS or mobile) are usually more specific, and you may want to optimize how and what data is being sent to those clients. This could result in messy controller code.
Go with the same controllers only when the API and pages you show match really well, and the thing is really simple.
If in doubt - build separate controllers. This does not hurt that much, sometimes more code is better than less - but convoluted code.
lukerollans
Hey there!
In my opinion, you should definitely create separate controllers for your API pipeline. As you’ve already said, setup your router to scope on
/apior similar andpipe_through :api, where yourapipipeline consists of at leastplug :accepts, ["json"]The alternative would be to pattern match on
connin a single controller and either render HTML or JSON views depending on the format request header or something. To me, this mixes concerns a bit too much and makes your pipelines much less flexible.garj
Thanks for the input guys!
OvermindDL1
You don’t need to pattern match in the controller. Phoenix already handles different views based on what the browser requests. For example when I do
render(conn, :request, blah_args: blah_args)then it will render my"index.html"template called viarenderifhtmlis requested, or it will call my render function that is matched on"index.json"for the JSON conversion (I also have others too).