The APIs produced by ash_json_api are JSON:API spec compliant, described here: JSON:API — Latest Specification (v1.1). You need to supply a specific content type header, which is described there in that spec 
application/vnd.api+json.
zachdaniel
Creator of Ash
1
stevensonmt
I think the header is set though:
iex(8)> Req.post("http://localhost:4000/api/json/artists", headers: ["content-type": "application/json"], json: %{"data" => %{"type" => "artist", "attributes" => %{"name" => "My New Artist", "biography" => "some content"}}})
{:ok,
%Req.Response{
status: 406,
headers: %{
"cache-control" => ["max-age=0, private, must-revalidate"],
"content-type" => ["application/vnd.api+json"],
"date" => ["Wed, 19 Feb 2025 18:18:45 GMT"],
"vary" => ["accept-encoding"],
"x-request-id" => ["GCWu5CBzLRfMtJUAAHyh"]
},
body: %{
"errors" => [
%{
"code" => "unacceptable_media_type",
"id" => "f2331603-19f4-4865-990a-169b0a7c68cc",
"meta" => %{},
"status" => "406",
"title" => "Unacceptable Media Type"
}
],
"jsonapi" => %{"version" => "1.0"}
},
trailers: %{},
private: %{}
}}
FWIW the response is the exact same (including the content type field) whether I include the headers: ["content-type" => "application/json"] in the request or not.
0
zachdaniel
Creator of Ash
stevensonmt
zachdaniel
Creator of Ash
it’s a weird/unexpected quirk of JSON:API 
arcanemachine
I got an email mentioning that the final version of the book has been released.
Congrats to @sevenseacat and @zachdaniel!
9
sevenseacat
Author of Ash Framework
pennychase
JEG2
Author of Designing Elixir Systems with OTP
Exactly! We’re reading it now and our first discussion about it is in two weeks. @sevenseacat and @zachdaniel are very welcome to join our chats if they have time and interest. Absolutely no pressure intended!
1
