<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Firstclasspostcodes</title>
    <description>The latest articles on DEV Community by Firstclasspostcodes (@firstclasspostcode).</description>
    <link>https://dev.to/firstclasspostcode</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F2725%2F84ce7c4e-3519-454f-a1be-eb9f4e5640b3.png</url>
      <title>DEV Community: Firstclasspostcodes</title>
      <link>https://dev.to/firstclasspostcode</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/firstclasspostcode"/>
    <language>en</language>
    <item>
      <title>Controlling access to your API Key</title>
      <dc:creator>David Kelley</dc:creator>
      <pubDate>Tue, 21 Jul 2020 15:13:24 +0000</pubDate>
      <link>https://dev.to/firstclasspostcode/controlling-access-to-your-api-key-2fgi</link>
      <guid>https://dev.to/firstclasspostcode/controlling-access-to-your-api-key-2fgi</guid>
      <description>&lt;p&gt;The Firstclasspostcodes &lt;a href="https://dashboard.firstclasspostcodes.com"&gt;dashboard&lt;/a&gt; provides you with a number of security controls that help restrict access with your API key.&lt;/p&gt;

&lt;h2&gt;
  
  
  Enabled Operations
&lt;/h2&gt;

&lt;p&gt;Today, we're releasing this to all of our customers! We've heard feedback from our customers asking us to provide a mechanism to disable operations that aren't required for their use cases, such as Geolocation Lookup; this can help to prevent accidental usage.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--BdK8GuH3--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/h7i3n7urgh2gng8n88ls.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--BdK8GuH3--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/h7i3n7urgh2gng8n88ls.png" alt="A view of security mechanisms"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let's also review all of the other ways we help to secure your API key.&lt;/p&gt;

&lt;h2&gt;
  
  
  Whitelisted domains
&lt;/h2&gt;

&lt;p&gt;You can control access to your API key by whitelisting domains that you'll be using the API key on. For example, if your website lives on &lt;code&gt;https://e-shop.com&lt;/code&gt;, you can restrict access by setting &lt;code&gt;e-shop.com&lt;/code&gt; as a whitelisted domain.&lt;/p&gt;

&lt;p&gt;This would prevent access to your API key for requests originating from any domain other than &lt;code&gt;e-shop.com&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;We also allow you to use wildcard subdomains, so feel free to provide &lt;code&gt;*.e-shop.com&lt;/code&gt; too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Whitelisted IPs
&lt;/h2&gt;

&lt;p&gt;If you're integrating with our API from the back-end, you can provide whitelisted IPs and CIDR ranges to restrict access to your API key from any requests not matching that IP or address range.&lt;/p&gt;




&lt;p&gt;We're also working on a mechanism to limit the number of requests that can be sent for a specific operation within a billing period.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
