Skip to contentAPILayer: production APIs with free plansExplore APILayer
nu:legal Deutsches Recht logo

Is nu:legal Deutsches Recht API down?

Current status, daily uptime history and troubleshooting for the nu:legal Deutsches Recht API (Government).

No, nu:legal Deutsches Recht is up

nu:legal Deutsches Recht answered our last daily check (Nov 15, 2026, 13:58 UTC) in 613 ms with HTTP 200.

Checking nu:legal Deutsches Recht now…

Sending a request from our server.

nu:legal Deutsches Recht API uptime history

30 days agoLatest check
Uptime
100% of 10 checks
Last check
Nov 15, 2026, 13:58 UTC
Response
613 ms · HTTP 200
Last up
Now

We check nu:legal Deutsches Recht's listed URL (https://recht.nulegal.eu/developers) once a day. History started when nu:legal Deutsches Recht was first checked, so new entries show fewer than 30 days.

nu:legal Deutsches Recht API not working for you?

  1. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  2. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  3. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Government APIs up at their last check

  1. 1EU VAT Rates by Commodity Code logo

    EU VAT rates mapped to CN and CPA commodity codes, all 27 member states.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2MORVS logo

    MORVS API

    Online · 1121 ms

    Source-linked US regulatory and public records: SEC filings, enforcement actions, recalls.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3Tollmint logo

    Tollmint API

    Online · 1163 ms

    Advertising, subscription, AI-disclosure and accessibility rules across the US, EU and UK.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4

    US Per Diem API

    Online · 660 ms

    GSA lodging and M&IE per diem rates for US cities by ZIP, state and fiscal year.

    • No API key needed
    • 100% uptime (30 days)
    • Returns JSON at its URL
    • Callable from the browser (CORS)
    No authHTTPSCORS
  5. 5Veridion logo

    Veridion API

    Online · 892 ms

    US congressional stock-trade disclosures and the President's OGE reports, linked to each filing.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all nu:legal Deutsches Recht alternatives · APIs down right now

nu:legal Deutsches Recht API status FAQ

Is nu:legal Deutsches Recht API down right now?

nu:legal Deutsches Recht answered our last daily check (Nov 15, 2026, 13:58 UTC) in 613 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether nu:legal Deutsches Recht is responding at this moment.

How do you check whether nu:legal Deutsches Recht API is up?

Once a day our checker requests nu:legal Deutsches Recht's listed URL (https://recht.nulegal.eu/developers) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.

How reliable is nu:legal Deutsches Recht API?

nu:legal Deutsches Recht answered 100% of our last 10 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.

What can I use if nu:legal Deutsches Recht API is down?

Free Government APIs that were up at their last check include EU VAT Rates by Commodity Code, MORVS, Tollmint. See the full list of nu:legal Deutsches Recht alternatives for a comparison.

Why does nu:legal Deutsches Recht API work for others but not for me?

A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If it works from one network but not another, check firewalls, VPNs and regional blocks. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.