<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Government Data on API Coding</title>
    <link>https://apicoding.com/tags/government-data/</link>
    <description>Recent content in Government Data on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/government-data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Querying USAspending for Federal Contract Awards With a POST Search and No API Key</title>
      <link>https://apicoding.com/querying-usaspending-for-federal-contract-awards-with-a-post-search-and-no-api-key/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/querying-usaspending-for-federal-contract-awards-with-a-post-search-and-no-api-key/</guid>
      <description>&lt;p&gt;USAspending publishes every federal award the United States government makes, and the API needs no key, no registration and no authorization header. That combination is rare enough on government data that it is worth saying twice.&lt;/p&gt;&#xA;&lt;p&gt;The thing that stops most people is the shape of the request. The interesting endpoints are POST, the body is a nested object, and a wrong field name gets you a 400 with little explanation. Here is the working version.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
