alxvallejo
Hey all,
I’m trying to make a GET request while passing in body params. One param requires a list of strings. The API documentation states:
curl -s --user 'api:YOUR_API_KEY' -G \
https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/stats/total \
-d event='accepted' \
-d event='delivered' \
-d event='failed' \
-d duration='1m'
In Elixir, here is how I’m preparing the body:
body =
%{event: ["accepted"]}
|> Plug.Conn.Query.encode
However the response I get is:
** (Bamboo.ApiError) There was a problem sending the email through the Mailgun API.
Here is the response:
"{\"message\":\"please provide at least one event: Missing mandatory parameter: event\"}\n"
Here are the params we sent:
"event[]=accepted"
Any ideas on what i’m doing wrong here?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
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.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
chulkilee
First, that curl is not using body. See
-Goption - it uses data under-das query parameter.If you use
-voption in curl - you can see the data are in the query string -?event=accepted&event=delivered&event=failed&duration=1mOkay - so you just need to build the query parameter then. You can use URI.encode_query/1.
Note
I really like the design of Elixir standard lib here - query parameter should not be implemented as map (as duplicate key is possible) and the order is preserved (as in keywords), and no magic transformation (e.g. passing list as value) . I saw many “easy to use” http interface are based on wrong assumption on many details…
dimitarvp
What kind of list? Comma-separated? Or a JSON-style list?
If the latter, your parameter can be encoded like so:
A lot of framework backends – Plug (and thus Phoenix) included – will decode the above as
event=[1,2,3].sb8244
Can you include the code that calls out to Mailgun? I see the query preparation, but not how that is actually being sent along. My initial guess is that maybe that part is not setup correctly.
Do you mean query params? GET requests technically can have a body, but I would put the chances of a service respecting it very low.