Queimadas INPE

Access to heat focus data (probable wildfire)

Open documentation ↗

No keyHTTPSNo CORSGeocoding

Checked today: not responding

API key

Not required

HTTPS

Supported

Browser calls

No, needs a proxy

Status

Failing · 0/100

Overview & Architectural Role

Queimadas INPE provides programmatic access to access to heat focus data (probable wildfire). Delivered over secure HTTPS protocols, it exposes structured endpoints designed to integrate cleanly into modern frontend frameworks, backend microservices, and automated data pipelines without requiring local database provisioning.

Who it is built for

Engineers building web dashboards, mobile applications, CLI utilities, or background cron workers in need of reliable geocoding data feeds.

Architectural Advantage

Consuming Queimadas INPE removes the operational overhead of running custom scrapers, orchestrating headless browser fleets, or manually seeding and maintaining a local database. Instead of reverse-engineering volatile DOM layouts or dealing with anti-bot IP blocks, your application connects directly to a standardized JSON interface designed for backend ingestion with consistent schema schemas. Zero-authentication access allows rapid prototyping and zero-credential static deployments.

What our checks found

Health score: 0/100
Reliability: 0%
Average latency: 11284ms

Last checked 2026-10-24. Measured independently, not self-reported by the provider.

Core Use Cases & Architecture Ideas

Practical real-world patterns for integrating Queimadas INPE into software systems.

Autocomplete Address & Location Form

Prevent shipping errors by resolving postal codes and street addresses into standardized coordinates during signup or checkout.

Architecture: Debounced client-side input calls an internal proxy route connected to Queimadas INPE, returning instant coordinate suggestions.

Store Locator & Proximity Matcher

Calculate the closest physical branches or delivery hubs based on user-provided city names or latitude/longitude.

Architecture: Backend geocodes user input via Queimadas INPE, then executes spatial PostGIS queries to return the top nearest facilities sorted by distance.

Interactive Travel & Route Visualizer

Plot points of interest, tourist paths, or elevation profiles dynamically on Leaflet/MapLibre map canvases.

Architecture: Single-page web client ingests geospatial GeoJSON boundaries from Queimadas INPE and renders vectorized overlays onto map layers.

Code Implementation Examples

Production-ready starting templates with error handling for Queimadas INPE.

// No authentication required.
// Modern native fetch with error handling
async function callApi() {
  try {
    const response = await fetch('https://queimadas.dgi.inpe.br/api/v1/resource', {
      method: 'GET',
    headers: { Accept: 'application/json' },
    });

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}: ${response.statusText}`);
    }

    const data = await response.json();
    console.log('Response payload:', data);
    return data;
  } catch (error) {
    console.error('API request failed:', error);
    throw error;
  }
}

// callApi();

This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.

Response Payload & Live Testing

Inspect the expected JSON structure returned by Queimadas INPE.

Expected JSON Response Payload

Authentic sample payload structure to evaluate schema attributes before integration.

{
  "query": "San Francisco, CA",
  "results": [
    {
      "formatted_address": "San Francisco, California, USA",
      "lat": 37.7749,
      "lon": -122.4194,
      "timezone": "America/Los_Angeles",
      "postal_code": "94102"
    }
  ],
  "total_matches": 1
}

Format: application/json

Integration Considerations & Best Practices

Technical factors to keep in mind when integrating Queimadas INPE into production environments.

Implement In-Memory or Edge Caching

Avoid triggering rate limits on public feeds by caching response payloads in Redis, Vercel KV, or standard HTTP Cache-Control headers with a 5-to-15 minute TTL.

Zero-Credential Environment Protection

While no API key is required, public keyless pools often share global rate limits. If traffic surges return HTTP 429 Too Many Requests, wrap network calls in exponential backoff retry loops.

CORS Proxy Required for Browser Frontend Calls

This API does not send Access-Control-Allow-Origin response headers. Direct fetch() calls from browser JavaScript will fail due to Same-Origin Policy. Route your calls through a server backend or lightweight edge proxy.

Validate HTTP Status Before Parsing JSON

Always inspect response.ok before executing response.json(). Upstream services returning 4xx or 502 Bad Gateway often serve HTML error pages, which cause syntax errors when parsed as JSON.

Where this listing comes from

Find IP address location information

No keyCORSHTTPS

Verified today: 100% uptime

View Details

Queimadas INPE — common questions

Answered from what our own scheduled checks found, not from the provider's marketing.

Is Queimadas INPE free to use?

Queimadas INPE is listed in our free catalogue and required no credential when we called it. It needs no authentication at all, so you can send a request without signing up. Free tiers can still carry rate limits or non-commercial terms, so check the provider's own terms before shipping.

Does Queimadas INPE need an API key?

No. We called Queimadas INPE on 2026-10-24 with no key, no token and no Authorization header, and it responded. That is what puts it in our no-key collection.

Can I call Queimadas INPE from browser JavaScript?

Not directly. Queimadas INPE did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.

Is Queimadas INPE still working?

Not at our last check on 2026-10-24. Queimadas INPE did not respond successfully, which is why it is marked as down here. This may be temporary; we re-check on a schedule and the badge above reflects the most recent run.

Is Queimadas INPE available over HTTPS?

Yes. Queimadas INPE serves over HTTPS, so you can call it from a secure page without triggering a mixed-content block.