Private API

US Zipcode, County, City, and State Boundaries API: A simple & very fast API that will allow you to integrate multiple GeoJson US boundaries results into your apps and systems. This API is designed to be used programatically for optimal performance. When using the MashApe UI for queries expect significant latency issues on large result sets!

  • New Feature Coming in 2018.

    published a year ago

    Happy Holidays!

    At the start of the new year, we will be releasing some new API Features.

    Many thanks to for assisting with the development & testing of these new features API. Influence Healthcare develops Healthcare's leading consumer experience platform.


    New query Parameter “showDetails”

    Description: Shows the County, State and the Zipcode FIPS. Also, it will show all counties associated with that zipcode. Example the zipcode: '57717' overlaps 4 counties "Butte","Harding", "Lawrence" and "Crook"

    Query Example: /rest/v1/public/boundary?and=false&showDetails=true&zipcode=57717'


    New query Parameter “showCenter” Description: Show's the centroid of all polygons of a zipcode.

    Query Example: .../rest/v1/public/boundary?showCenter=true&zipcode=10004'


    Search by a FIPS

    Description: Search for all zipcodes by FIPS.

    Query Example: /rest/v1/public/boundary/fips/01117'


    Additional Polygon for zipcodes that have no Official polygon Description: Special zipcodes are now shown if they do not have a valid polygon from the US Census we now generate a Polygon( Small Circle ) for that zipcode.

    Query Example: .../rest/v1/public/boundary?and=false&zipcode=20050'


    Try the new API in on our Beta Server:

  • Psst! Want a free Month on us?

    published a year ago


    Please send us your username, screenshot(s), and a brief description of your product/system to Then we will credit your next month membership charge.:) We plan to use the screenshots and your product profile in our marketing material(facebook,etc.) which will mean free advertisement for you as well!

    Thank you! Beth,

  • Release 1.2: New Features

    published a year ago
    • We now include 2013,2014,2015 and 2016 Postal Boundaries from the US Census.

    • Query by postal boundaries by bounding box( ./rest/v1/public/boundary/boundingbox?north-east=<required>&south-west=<required>' ) , limit results are 500 us if this is a concern!

    • Showing the radius is disabled by default on(./rest/v1/public/boundary/location?latitude=38.696142&longitude=-104.939744&radius=1&showCirlce=false')

    Please email us any questions or concerns, we would love to hear from you!

    Also, always looking for screen shots of products/systems/mobile apps using our API , shoot us a quick email with a screen grab so we can publish.

    Thank you! -Beth

  • Performance and the mashape UI.

    published a year ago

    *The "mashape UI" does not work well when querying large results.

    Please use our API within your application or system programmatically for optimal performance! Email with any questions. Thank you!

  • Update 1.2 released!

    published 2 years ago

    **We are now using 2016 US Postal boundaries(Not P.O boxes) from the US government.

    **We've implemented a new feature that shows zipcodes withing a specified radius by miles. Perform a radius query to return back all of the zip codes that are contained within OR intersect the radius in miles with one line of code: .../rest/v1/public/boundary/location?latitude=38.696142&longitude=-104.939744&radius=20'

    Results image:

    If you have any questions or concerns please email mail us for a faster response

    Thank you!

  • New Feature(beta testing). Query by Radius

    published 2 years ago

    Try on our beta environment: Radius query to return back all of the zip codes that are contained within OR intersect the radius in miles.

    one line of code: /rest/v1/public/us-boundaries-io/location?latitude=38.696142&longitude=-104.939744&radius=8'

    results images:

  • Success Stories

    published 2 years ago

    Happy Monday!

    We are writing a few tech articles about and would love to include some success stories. This of course would be great advertising for your business as well! Please shoot us an email if you would like your business to be mentioned with a few sentences on how our API is used within your business or service. Screenshots are a plus!


  • How to determine how any requests you have left under your plan per day, this will help protect against overage charges

    published 2 years ago

    In the response header(s) after you make a call you can inspect how many request you have left under your plan by obtaining the value from "X-Ratelimit-Requests-Remaining:" example: X-Ratelimit-Requests-Limit: 100 X-Ratelimit-Requests-Remaining: 94

    Also, If you start to go over your allowed requests. You should receive an email from mashape like below:

    "Your business must be doing well! At this time you have consumed all of the allocated API calls under your ULTRA subscription to the API. If you continue to make calls this month, you will incur overage fees. We strongly recommend that you upgrade to a pricing plan with a higher quota."

    if you think you may go over our mega plan, please send us an email for a custom plan.


    Please email me with any questions or concerns.

    -Beth Morgan

  • 2014, and 2015 US ZipCode Boundary data.

    published 2 years ago

    We are now processing 2014, and 2015 US Census/TIGER data from the United States Government.

    Any questions please email us


  • Our Beta API is back online.

    published 3 years ago
  • New Clients

    published 3 years ago

    A reminder, our API sits behind the “MashApe” User interface which has performance issues when large results are returned from any API. So we default to '30' Zipcode limit using the 'limit' query parameter in the User Interface->Documentation tab. When using the API within your client code, this query parameter is not required.

    If you have any questions or concerns please contact us

    Thank you! Beth.

  • Canada Postal Boundaries are coming soon....

    published 3 years ago

    Please reach out to us if you have any questions or would like to beta test.

    Thank you!

    Like us:

  • A Reminder.

    published 3 years ago

    *The "mashape UI" does not work well when querying large results. Please user our API within your application or system! Email with any questions. Thank you and Happy New year!

  • Beta Test 1.2.0.

    published 3 years ago

    Join for free:

    We have a new capability that will allow more complex queries to be performed using our boundaries API. Query for all zipcode boundaries that are part of Suffolk, and Nasau Counties only in New York. example query: …/boundary?and=false&state=NY&county=suffolk, nassau&with-and=state

    with-and , and with-or new properties allowed values are state, city, zipcode,and county.


    like us:

  • Upgrade to 1.1 Released this morning.

    published 3 years ago

    [Bug fixes] none reported.

    [Improvements] Increased performance. Added new region to support reliability.

    If you experience any issues with this upgrade please don't hesitate to email us

    Thank you.

  • Security upgrade today.

    published 3 years ago

    Today we installed some additional software to increase our firewall security which may have effected some users in querying our API. The issue has been resolved.

    If you have any questions or concerns please email them

    Thank you for using and Happy Holidays!

  • Google Data layers

    published 3 years ago

    This is a good overview on how to integrate boundaries-io with Google Data layers:

  • Performance using unirest-x libraries.

    published 3 years ago

    If you are building client applications for performance do NOT use the current unirest-java library. We recommend to simply use the Apache HTTPClient 4.3.x library instead. We discovered significant performance degrade using this unirest-java library.

    sample code:

    import org.apache.http.client.ClientProtocolException; import org.apache.http.client.methods.CloseableHttpResponse; import org.apache.http.client.methods.HttpGet; import org.apache.http.impl.client.CloseableHttpClient; import org.apache.http.impl.client.HttpClients;

    CloseableHttpClient httpclient = HttpClients.createDefault();

    HttpGet httpGet = new HttpGet(",VA&includepostal=false");

    httpGet.setHeader("X-Mashape-Key", "YOUR MASHAPE KEY");

    httpGet.setHeader("Accept", "application/json");

    CloseableHttpResponse response = httpclient.execute(httpGet);

  • Would love to hear from you!

    published 3 years ago

    We are in the process of building a company website and would love to included some great testimonial and use-cases our API is solving for our clients. If you would like to be included in this please drop us a line with an 'logo' from your company!

    Please email us if you have any feature requests.

    Thanks for using boundaries-io and uk.boundaries-io;

  • We've created a quora page, stop by and follow us!

    published 3 years ago

    Thank you for supporting our API.

    To further develop and continue service, please subscribe to a paid membership.

  • 1.0 Released.

    published 3 years ago

    [Features] -Significantly increased performance of the API

    [Bugs Fixes] -No Bugs reported. -If you experience any bugs please report in API Support. Thanks!

    Want a feature? email us

    Thanks for your support!

  • UK Boundaries Released.

    published 3 years ago

    Query for postal boundaries in the United Kingdom.

    UK Postal Code(ex. ZE1 0AE) ,Sector, District, City, and Wards Boundaries API

    Thanks everyone for the continued support!

  • Simple Price Plan enabled

    published 3 years ago

    Hi All,

    We had a lot of data harvester(s) to use our API recently, so we needed to put a reasonable price plan in place.

    Please leave feedback in the API Support Link.

    Thanks for your support!


    published 3 years ago


    [Bugs Fixes] -No Bugs reported. -If you experience any bugs please report in API Support. Thanks!

    [Improvements] -When testing the API using the MashUI Interface users experienced hangs,and "End point not working", we added a limit query parameter that defaults to 50 when using MashApe UI directly as a workaround when testing.. This is an optional parameter so no code changes are required to your code.

  • 0.9.3 Released.

    published 3 years ago

    [Features] Return Post Box/unique locations(lat,long) for zipcodes that do not have an postal boundary(polygon).

    by including the "includepostal=true" in query parameter geojson will now include post box/unique locations

    example results in google map:

    if you have a feature request please note in API Support. Thanks!

    [Bugs Fixes] -No Bugs reported. -If you experience any bugs please report in API Support. Thanks!


  • "Sorry, it appears the endpoint is not responding :(" From MashApe UI.

    published 3 years ago

    Hello Developers!

    Thanks for using our API!

    If you get the error message while testing the API via Mashape "Sorry, it appears the endpoint is not responding :(" our API is actually working very well! We are returning a large result set that the MashApeUI cannot handle so it produces this message. Please use the API directly within your applications/systems for large results sets to avoid this error.


  • Feature Request Submission

    published 4 years ago


    Please submit Feature requests , instead of emailing.


  • 0.9.2

    published 4 years ago


    [Bugs] -Now rerturns Multiple Polygon feature types for zipcodes that contain multiple polygons(boundaries.)


  • 0.9.1 Version was deployed.

    published 4 years ago



    [Improvements] -Increased memory on all nodes.

  • We now support querying by a US County.

    published 4 years ago

    Example query:

    Image of the results in GooleMap:

    please note that some zipcodes do not fall within a county.

  • MashApe UI vs. Programmatically using the API

    published 4 years ago

    If you expecting large amounts of data from a query, you must programmatically call the API to process the data. The Mashape UI does not handle large amounts of data.