Documentation menu
Docs / Reference / Search storage tanks and leaking-tank releases

Search storage tanks and leaking-tank releases

GET/storage_tank

Parameters

ParameterTypeDescription
qstringoptionalFull-text search across the indexed fields of the record, including names (business, establishment, vendor, contractor) wherever the dataset carries them, e.g. q=brewery or q="Iron Hill". This is the name search: there is no separate name= parameter, and it works on every plan including free. It matches the BUSINESS or trade name, the address, city, county and licence/permit number. It does NOT match an owner, licensee or applicant's personal name: these datasets carry public business records only and never store an individual's name, so searching for a person returns nothing. Space-separated words require all terms (e.g. "wood panel"). Use OR to match any term ("wood OR panel OR acoustic"), quotes for exact phrases ("supply arrangement"), and a leading minus to exclude ("software -hardware").
categorystringoptionalProcurement category: CNST, GD, SRV, SRVTGD. For recalls: product category (e.g. 'Baby products', 'Toys and games'). For healthcare: facility category (acute, long_term, home, behavioral, outpatient, specialty). For storage tanks: record type (tank or release).
statusstringoptionalFilter by status. Contracts/tenders: Active, Expired, Cancelled, Open (exact). Permits: use a status_canonical value instead (issued, in_review, completed, expired, cancelled, unknown).
substancestringoptionalFilter by pollutant substance name (release)
citystringoptionalFilter by city. For the US liquor/healthcare/storage-tank datasets this is a distinct filter (exact, case-insensitive). For all other datasets it is an alias for municipality.
countystringoptionalFilter by county. Exact, case-insensitive (liquor, healthcare, storage-tank).
statestringoptionalFilter by 2-letter US state code, e.g. FL, CA, TX (healthcare, liquor, storage-tank).
issued_afterstringoptionalFilter by report date >= YYYY-MM-DD (reported_date). Aliases: date_from, date_after
issued_beforestringoptionalFilter by date <= YYYY-MM-DD. Aliases: date_to, date_before
latnumberoptionalLatitude for proximity search. Send with lng.
lngnumberoptionalLongitude for proximity search. Send with lat.
radius_kmnumberoptionalRadius in km, 0.1 to 25. Optional: lat and lng with no radius search 1 km around the point. The radius actually applied is returned as radius_km in the response, so a default is never silent. For every record at one street address rather than everything near it, use /property.
sort_bystringoptionalSort field: published (publication_date, tenders only), date (event date; this is award_date for contracts/awards), value (the entity's value field), closing (closing_date for tenders)
sort_orderstringoptionalSort order: asc or desc
limitintegeroptional
offsetintegeroptional
cursorstringoptionalPagination cursor from next_cursor in a previous response. Use instead of offset for deep pagination.

Request

curl --request GET \
  --url 'https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank' \
  --header 'x-rapidapi-host: tankscreen-us-storage-tank-data.p.rapidapi.com' \
  --header 'x-rapidapi-key: YOUR_RAPIDAPI_KEY'
import requests

url = "https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank"
headers = {"x-rapidapi-host": "tankscreen-us-storage-tank-data.p.rapidapi.com", "x-rapidapi-key": "YOUR_RAPIDAPI_KEY"}
resp = requests.get(url, headers=headers)
print(resp.json())
const res = await fetch("https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank", {
  headers: {
    "x-rapidapi-host": "tankscreen-us-storage-tank-data.p.rapidapi.com",
    "x-rapidapi-key": "YOUR_RAPIDAPI_KEY",
  },
});
const data = await res.json();
console.log(data);
<?php
$ch = curl_init("https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "x-rapidapi-host: tankscreen-us-storage-tank-data.p.rapidapi.com",
    "x-rapidapi-key: YOUR_RAPIDAPI_KEY",
]);
echo curl_exec($ch);
require "net/http"
require "uri"

uri = URI("https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank")
req = Net::HTTP::Get.new(uri)
req["x-rapidapi-host"] = "tankscreen-us-storage-tank-data.p.rapidapi.com"
req["x-rapidapi-key"] = "YOUR_RAPIDAPI_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body
package main

import (
    "fmt"
    "io"
    "net/http"
)

func main() {
    req, _ := http.NewRequest("GET", "https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank", nil)
    req.Header.Add("x-rapidapi-host", "tankscreen-us-storage-tank-data.p.rapidapi.com")
    req.Header.Add("x-rapidapi-key", "YOUR_RAPIDAPI_KEY")
    res, _ := http.DefaultClient.Do(req)
    defer res.Body.Close()
    body, _ := io.ReadAll(res.Body)
    fmt.Println(string(body))
}
import java.net.URI;
import java.net.http.*;

HttpRequest req = HttpRequest.newBuilder()
    .uri(URI.create("https://tankscreen-us-storage-tank-data.p.rapidapi.com/storage_tank"))
    .header("x-rapidapi-host", "tankscreen-us-storage-tank-data.p.rapidapi.com")
    .header("x-rapidapi-key", "YOUR_RAPIDAPI_KEY")
    .build();
HttpResponse<String> res = HttpClient.newHttpClient()
    .send(req, HttpResponse.BodyHandlers.ofString());
System.out.println(res.body());

Response fields

One storage_tank record. Measured over 6,000 live records sampled across municipalities. Percentages say how often each field is populated: sources publish different columns, so a field missing from a given record is normal rather than an error.

FieldTypeDescription
addressstringPopulated in 99% of sampled records.
agencystringAlways present.
citystringPopulated in 90% of sampled records.
closed_datestringPopulated in 13% of sampled records.
countystringPopulated in 74% of sampled records.
facility_idstringPopulated in 87% of sampled records.
facility_namestringPopulated in 99% of sampled records.
facility_typestringPopulated in 37% of sampled records.
fetched_atstringWhen Nimbus last ingested this record. Bookkeeping, not source data. Always present.
latitudenumberPopulated in 79% of sampled records.
longitudenumberPopulated in 79% of sampled records.
municipalitystringCity slug. Call /{entity_type}/coverage for every slug in this dataset. Always present.
record_idstringStable identifier for this record. Pass it to the /{entity_type}/{record_id} endpoint. Always present.
record_typestringAlways present.
reported_datestringPopulated in 63% of sampled records.
statestringAlways present.
statusstringPopulated in 70% of sampled records.
status_canonicalstringStatus mapped onto a shared vocabulary. This is what the status_canonical filter matches. Always present.
substancestringPopulated in 31% of sampled records.
zip_codestringPopulated in 67% of sampled records.
1 more fields published by only one or two cities

Present on under 10% of records. Useful when you are working with a specific city, not something to rely on across the dataset.

FieldTypePopulated
tank_countstring9.9%

Errors

Every error returns {"detail": "…"}, a sentence naming what was wrong and, where there is one, the fix.

StatusWhen
400The request is understood but cannot be served as asked, e.g. offset above 9500, or cursor combined with sort_by=value. The message names the fix.
403Missing or invalid API key.
404No such endpoint, or no record with that id.
422A parameter is invalid: an unknown city slug, an impossible date, a limit above 500, an unrecognised sort field, or a misspelled parameter name. The message names the parameter and, where there is one, the nearest valid value.
429Rate limit or plan quota exceeded.
500Unexpected server error.
504The query took too long. Narrow it with a municipality or a date range.
Ready to build?Subscribe on RapidAPI to get your key and start calling TankScreen in minutes.
Get your API key →