Speaking generally, it&#x27;s more difficult to do much useful with that, because it&#x27;s hard to do much more than route on the URL. You could prototype code that merely looks at the mentioned headers, but it&#x27;s getting kinda silly at that point.<p>More specific to JSON, you may be looking for something like <a href="https:&#x2F;&#x2F;mholt.github.io&#x2F;json-to-go&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mholt.github.io&#x2F;json-to-go&#x2F;</a> (by the same author) or <a href="https:&#x2F;&#x2F;github.com&#x2F;ChimeraCoder&#x2F;gojson" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ChimeraCoder&#x2F;gojson</a> (which I&#x27;ve used myself).<p>(I find that what I pay in using a static language like Go to manipulate JSON and having to use a tool like that often comes back to me pretty quickly when I take the tool output as a template and start turning all the structs into Real Objects (TM). The dynamic languages are pretty good at taking JSON and yielding a simple pile of dict&#x2F;map&#x2F;array&#x2F;strings&#x2F;numbers&#x2F;etc., but if you want to get real objects back out of them the advantage over Go evaporates. Not because the dynamic languages make it &quot;hard&quot;, but just because with one of these tools, both Go and the dynamic solutions are roughly as easy.)