Documentation

The Adios API gives the news of every major Croatian portal as data: the latest and biggest stories, search by meaning, everything connected to a question, news around any place, the map, timelines, daily summaries, trending topics and product recalls.

Quickstart

1. Make a key
   Sign in to Adios and open the console. Your first key is made at once; it is shown only once.
2. Call the API
   Copy

   export ADIOS_KEY="adios_…"
   curl "https://adios.hr/api/v1/articles?sort=most_covered&limit=5" -H "Authorization: Bearer $ADIOS_KEY"

3. Read data
   Every answer is {"data": …, "meta": …}; data is an object or a list, meta tells how many items and what the plan limited.

Authentication

Send the key in a header, either way:

Authorization: Bearer adios_AbC123…
X-Api-Key: adios_AbC123…

• A key is "adios_" and 40 letters and digits. We keep only its hash (SHA-256), so it can't be shown again: revoke a lost key and make a new one.
• Up to 10 active keys per account (e.g. one for production, one for testing). A revoked key stops working at once.
• Don't put a key in public page or app code: call the API from your server.
• Only the MCP also takes the key in the address (/api/mcp?key=adios_…), as ChatGPT and Claude can't set a header.

Limits

Each plan has a per-minute and a per-day limit, and the costlier calls (search, connected, places) have their own daily limit too. The day starts at 00:00 UTC.

Every answer carries the state in headers:

X-RateLimit-Limit: 5000          # daily limit
X-RateLimit-Remaining: 4987      # left today
X-RateLimit-Reset: 1760227200    # when the count resets (Unix)
X-RateLimit-Minute: 60
X-RateLimit-Group: geo           # for the costlier calls
X-RateLimit-Group-Limit: 1000
X-RateLimit-Group-Remaining: 992

When a limit is reached the answer is 429 with a Retry-After header (seconds). If you ask beyond the plan (a bigger radius, more items, further back), you get what the plan allows and meta says so (e.g. radius_limited_to).

Responses

{
  "data": [ … ],
  "meta": {
    "count": 20,
    "limit": 20,
    "plan": "free",
    "took_ms": 41
  }
}

• Lists have limit and offset (stories: page). Empty fields are left out.
• url is the page on Adios (summary, every portal, the map); source.url is the article on the portal.
• Every list (search, connected, nearby, city, map and stories too) leaves out filler: horoscopes, quizzes, reality shows, celebrity gossip and promos. include_filler=true brings it back in any call.

Errors

{ "error": { "code": "invalid_parameter", "message": "'lat' must be a number between -90 and 90.", "docs": "https://adios.hr/developers/docs#errors" } }

News

curl "https://adios.hr/api/v1/articles?category=crime&limit=5" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/articles/{id}" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/search?q=po%C5%BEar%20Split&limit=5" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/connected?q=cijene%20goriva" \
  -H "Authorization: Bearer $ADIOS_KEY"

Places and the map

curl "https://adios.hr/api/v1/nearby?place=Zadar&radius_km=50&hours=48" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/places/resolve?name=Dugom%20Selu" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/cities" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/cities/zadar" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/map?hours=6&urgent_only=true" \
  -H "Authorization: Bearer $ADIOS_KEY"

Summaries

curl "https://adios.hr/api/v1/digests/daily?date=yesterday" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/digests/weekly" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/digests/monthly" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/digests?kind=weekly&limit=4" \
  -H "Authorization: Bearer $ADIOS_KEY"

Stories (timelines)

curl "https://adios.hr/api/v1/stories?period=week" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/stories/{slug}" \
  -H "Authorization: Bearer $ADIOS_KEY"

More

curl "https://adios.hr/api/v1/trending" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/recalls?lang=en&limit=5" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/providers" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl "https://adios.hr/api/v1/categories" \
  -H "Authorization: Bearer $ADIOS_KEY"

Account

curl "https://adios.hr/api/v1/me" \
  -H "Authorization: Bearer $ADIOS_KEY"

Webhooks

curl "https://adios.hr/api/v1/webhooks" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl -X POST "https://adios.hr/api/v1/webhooks" \
  -H "Authorization: Bearer $ADIOS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Hotel Zadar","url":"https://example.com/adios","event":"nearby.story","place":"Zadar","radius_km":20,"urgent_only":true}'

curl -X DELETE "https://adios.hr/api/v1/webhooks/{id}" \
  -H "Authorization: Bearer $ADIOS_KEY"

curl -X POST "https://adios.hr/api/v1/webhooks/{id}/test" \
  -H "Authorization: Bearer $ADIOS_KEY"

Webhooks: events

A webhook is your HTTPS address Adios POSTs to when something happens, without you asking. Make one in the console or through the API (POST /v1/webhooks).

The delivery's body:

POST https://example.com/adios
Content-Type: application/json
Adios-Event: nearby.story
Adios-Delivery: nearby_3f2c…
Adios-Signature: t=1760180000,v1=5b2e…

{
  "id": "nearby_3f2c…",
  "type": "nearby.story",
  "created_at": "2026-10-11T18:04:00Z",
  "webhook_id": "9a1d…",
  "test": false,
  "data": {
    "place": "Zadar",
    "story": { "title": "…", "kind": "fire", "place": "Bibinje", "distance_km": 6.2, "url": "https://adios.hr/…", … }
  }
}

Verifying signatures

Every delivery is signed with your webhook's secret (see the console): v1 is HMAC-SHA256 of "{t}.{body}". Check the signature, and that t is no older than 5 minutes.

import crypto from "node:crypto";

function verify(secret, header, rawBody) {
  const parts = Object.fromEntries(header.split(",").map(p => p.split("=")));
  if (Math.abs(Date.now() / 1000 - Number(parts.t)) > 300) return false;
  const expected = crypto.createHmac("sha256", secret).update(`${parts.t}.${rawBody}`).digest("hex");
  return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1 ?? ""));
}

import hmac, hashlib, time

def verify(secret: str, header: str, raw_body: bytes) -> bool:
    parts = dict(p.split("=", 1) for p in header.split(","))
    if abs(time.time() - int(parts["t"])) > 300:
        return False
    signed = parts["t"].encode() + b"." + raw_body
    expected = hmac.new(secret.encode(), signed, hashlib.sha256).hexdigest()
    return hmac.compare_digest(expected, parts.get("v1", ""))

static bool Verify(string secret, string header, string rawBody)
{
    var parts = header.Split(',').Select(p => p.Split('=', 2)).ToDictionary(p => p[0], p => p[1]);
    long t = long.Parse(parts["t"]);
    if (Math.Abs(DateTimeOffset.UtcNow.ToUnixTimeSeconds() - t) > 300) return false;
    byte[] hash = HMACSHA256.HashData(Encoding.UTF8.GetBytes(secret), Encoding.UTF8.GetBytes($"{t}.{rawBody}"));
    return CryptographicOperations.FixedTimeEquals(
        Encoding.ASCII.GetBytes(Convert.ToHexStringLower(hash)), Encoding.ASCII.GetBytes(parts["v1"]));
}

function verify(string $secret, string $header, string $rawBody): bool {
    parse_str(str_replace(',', '&', $header), $parts);
    if (abs(time() - (int)$parts['t']) > 300) return false;
    $expected = hash_hmac('sha256', $parts['t'] . '.' . $rawBody, $secret);
    return hash_equals($expected, $parts['v1'] ?? '');
}

Delivery and retries

• Answer 2xx within 10 seconds. Anything else is a failure.
• A failed delivery is retried less and less often (1, 2, 4… up to 60 minutes); after 20 failures in a row the webhook is switched off, and you switch it back on in the console.
• Each event comes once (its id is stable, so duplicates are easy to spot). A new webhook starts from when it was made, with no old events.
• Adios checks for news every minute. The console's "Test" button sends a real example right away.
• Addresses must be https:// on the public internet.

MCP

Adios is an MCP server too (Model Context Protocol, Streamable HTTP). Every endpoint above marked MCP is also a tool, plus search and fetch (for ChatGPT connectors and deep research) and ready prompts (morning briefing, local news, explain a story, recalls).

Without a key it works for everyone (limits per session); with a key (a header or ?key=) your plan's limits apply and the calls are in your log.

Changelog

1.0 · 11 October 2026 · First version: news, search, everything connected, news nearby, the map, cities, summaries, timelines, trending topics, recalls, webhooks and an MCP for everyone.

Changes that could break your code are announced in advance; new fields in answers may come at any time.