Frequently asked questions about the Shovels platform.
For performance reasons, we limit the number of records you can export at a single time, for a single search, to 1000 records.
There is one workaround for this: break your query down into smaller segments (eg, change from state
to city
or zip code
) and then run each one separately. Combined, these can generate a CSV with more than 1000 records.
On the other hand, the Shovels API has no result limit, so you can export as many records as needed.
For similar performance reasons as above, we limit the number of results displayed on the map to 50, which is the maximum page size.
In order to view the next page of results in the map format, switch back to the “List View” and paginate as usual, and then switch back to “Map View”.
We talk about this issue in depth here, but the short of it is this:
If you’re seeing less-than-desired results, contact us and we’ll investigate which of the above reasons is the likely culprit, and how we might fix it for you.
The main difference is scale and depth of the data provided.
With the Shovels API, you can programmatically access the same high level data (objects like permits, addresses, contractors, etc), but with deeper data and fields for each one.
You can also export more records at a time, with greater control and flexibility with filters and parameters.
Beyond that, using the API allows for much more complex use cases, such as direct product integrations or query automation, which isn’t possible with Shovels Online.
Like any REST API, there are a wide variety of ways to use it: which one is best depends on your use case.
I’ll outline a few of the most common ways we see our users interact with the API today:
bash
or zsh
that’s great for making basic HTTP requests (among many others). Our API Reference playground has example queries in a variety of languages, including cURL.At the end of the day, there’s no right way to use it, and if you have any questions don’t hesitate to reach out to us for help!
We update our data monthly, but depending on your platform it may take some time for the actual data to arrive.
Here’s a rough timeline of what our data delivery looks like on any given month:
GET /meta/release
endpoint.This will vary based on delivery method (whether you’re getting a table share to your data warehouse or Amazon S3 bucket), but in general there will be a timestamp in the file or folder metadata indicating when it was last updated.
It will depend on the data included in the original report, and the nature of the new data that we’ve added to our system.
The safest best will be to Contact Sales as we handle these case-by-case.
Let us know if there’s anything else we can help you with! Our Support team is available to help you with any question you might have, just email us at support@shovels.com.
Frequently asked questions about the Shovels platform.
For performance reasons, we limit the number of records you can export at a single time, for a single search, to 1000 records.
There is one workaround for this: break your query down into smaller segments (eg, change from state
to city
or zip code
) and then run each one separately. Combined, these can generate a CSV with more than 1000 records.
On the other hand, the Shovels API has no result limit, so you can export as many records as needed.
For similar performance reasons as above, we limit the number of results displayed on the map to 50, which is the maximum page size.
In order to view the next page of results in the map format, switch back to the “List View” and paginate as usual, and then switch back to “Map View”.
We talk about this issue in depth here, but the short of it is this:
If you’re seeing less-than-desired results, contact us and we’ll investigate which of the above reasons is the likely culprit, and how we might fix it for you.
The main difference is scale and depth of the data provided.
With the Shovels API, you can programmatically access the same high level data (objects like permits, addresses, contractors, etc), but with deeper data and fields for each one.
You can also export more records at a time, with greater control and flexibility with filters and parameters.
Beyond that, using the API allows for much more complex use cases, such as direct product integrations or query automation, which isn’t possible with Shovels Online.
Like any REST API, there are a wide variety of ways to use it: which one is best depends on your use case.
I’ll outline a few of the most common ways we see our users interact with the API today:
bash
or zsh
that’s great for making basic HTTP requests (among many others). Our API Reference playground has example queries in a variety of languages, including cURL.At the end of the day, there’s no right way to use it, and if you have any questions don’t hesitate to reach out to us for help!
We update our data monthly, but depending on your platform it may take some time for the actual data to arrive.
Here’s a rough timeline of what our data delivery looks like on any given month:
GET /meta/release
endpoint.This will vary based on delivery method (whether you’re getting a table share to your data warehouse or Amazon S3 bucket), but in general there will be a timestamp in the file or folder metadata indicating when it was last updated.
It will depend on the data included in the original report, and the nature of the new data that we’ve added to our system.
The safest best will be to Contact Sales as we handle these case-by-case.
Let us know if there’s anything else we can help you with! Our Support team is available to help you with any question you might have, just email us at support@shovels.com.