Domain feed API reference and examples

This page describes every endpoint of the Domain Feed API. To get started, authenticate, check your plan’s limits or understand the errors, go to getting started. The values in the examples are made up.

Conventions

• Base URL: https://api.cifradia.com. Every data endpoint lives under /v1.
• Authentication: send the key in the Authorization: Bearer <your key> header, never in the URL. The examples read it from the KEY variable.
• Format: responses are JSON (/v1/dailyzip/ returns a ZIP). Parameters go in the query string; encode values with special characters such as % or | (curl --data-urlencode does it for you). For example, the wildcard % is written %25 in the URL: ?kw=%25bank%25.
• Dates: yyyymmdd in requests (for example 20260115) and yyyy-mm-dd in responses. All are UTC.
• Plan: your plan limits how far back you can go, which TLDs you can query and whether you can download the daily ZIP. Outside your plan, the API answers 403.
• Specification: the OpenAPI document is at api.cifradia.com/openapi.json.

export KEY="<your key>"

GET /v1/tlds

Lists the TLDs the feed works with, with their cumulative totals and the counts of each one’s latest update.

Parameters

Example

curl -H "Authorization: Bearer $KEY" "https://api.cifradia.com/v1/tlds"

Response

{
  "status": true,
  "records": 2,
  "data": [
    {
      "tld": "com",
      "domaincount": 1000,
      "total_added_count": 1200,
      "total_deleted_count": 200,
      "latest_add_count": 30,
      "latest_delete_count": 10,
      "last_processed": "2026-01-15"
    },
    {
      "tld": "net",
      "domaincount": 400,
      "total_added_count": 450,
      "total_deleted_count": 50,
      "latest_add_count": 12,
      "latest_delete_count": 4,
      "last_processed": "2026-01-15"
    }
  ]
}

Notes

• On a plan limited to certain TLDs, the list contains only those TLDs.
• records is the number of TLDs returned. domaincount is the cumulative net (added minus deleted); total_added_count and total_deleted_count are the cumulative gross figures; latest_add_count and latest_delete_count refer only to the latest processed update (last_processed).

GET /v1/added

Returns the domains newly registered on a date or over a date range, with filters by keyword, TLD and IDN.

Parameters

Example

curl -G -H "Authorization: Bearer $KEY" \
  --data-urlencode "kw=%bank%" \
  --data-urlencode "tlds=com,net" \
  --data-urlencode "date=20260115" \
  "https://api.cifradia.com/v1/added"

Response

{
  "status": true,
  "date": "2026-01-15",
  "records": 2,
  "source": "added domains",
  "data": [
    {
      "domain": "example.com",
      "name": "example",
      "tld": "com",
      "length": 7,
      "idn": 0,
      "ipv4": null,
      "date": "2026-01-15"
    },
    {
      "domain": "example.net",
      "name": "example",
      "tld": "net",
      "length": 7,
      "idn": 0,
      "ipv4": null,
      "date": "2026-01-15"
    }
  ]
}

Notes

• records is the total number of domains that match the filters, regardless of limit and offset. To walk a large result, repeat the request adding limit to offset until you reach records, and use sorton=domain: with the default order there are ties, so pages can repeat or skip domains.
• The response date is the reference date; each domain carries its own date, which matters when you ask for a range.
• domain is the full name (example.com) and name is the name without the TLD. idn is 0 or 1. ipv4 is optional and is null when there is no value.
• Added domains: a domain counts on the day we first detect it. The previous day’s changes are usually available around 07:30 UTC; this is a typical timing, not a guarantee.
• Your plan limits the history: a date before that limit gives 403, and a range that crosses it is clipped to the limit.

GET /v1/deleted

Returns the domains deleted on a date or over a date range, with filters by keyword, TLD and IDN.

Parameters

Example

curl -G -H "Authorization: Bearer $KEY" \
  --data-urlencode "kw=%bank%" \
  --data-urlencode "tlds=com,net" \
  --data-urlencode "date=20260115" \
  "https://api.cifradia.com/v1/deleted"

Response

{
  "status": true,
  "date": "2026-01-15",
  "records": 2,
  "source": "deleted domains",
  "data": [
    {
      "domain": "example.com",
      "name": "example",
      "tld": "com",
      "length": 7,
      "idn": 0,
      "ipv4": null,
      "date": "2026-01-15"
    },
    {
      "domain": "example.net",
      "name": "example",
      "tld": "net",
      "length": 7,
      "idn": 0,
      "ipv4": null,
      "date": "2026-01-15"
    }
  ]
}

Notes

• records is the total number of domains that match the filters, regardless of limit and offset. To walk a large result, repeat the request adding limit to offset until you reach records, and use sorton=domain: with the default order there are ties, so pages can repeat or skip domains.
• The response date is the reference date; each domain carries its own date, which matters when you ask for a range.
• domain is the full name (example.com) and name is the name without the TLD. idn is 0 or 1. ipv4 is optional and is null when there is no value.
• Deleted domains: a domain counts on the day we first detect it or it stops appearing. The previous day’s changes are usually available around 07:30 UTC; this is a typical timing, not a guarantee.
• Your plan limits the history: a date before that limit gives 403, and a range that crosses it is clipped to the limit.

GET /v1/history

Returns every added and deleted event of one domain, oldest first. If the domain was registered and removed several times, all of them appear.

Parameters

Example

curl -G -H "Authorization: Bearer $KEY" \
  --data-urlencode "domain=example.com" \
  "https://api.cifradia.com/v1/history"

Response

{
  "status": true,
  "domain": "example.com",
  "records": 2,
  "data": [
    { "event_type": "added", "date": "2024-03-02" },
    { "event_type": "deleted", "date": "2025-03-05" }
  ]
}

Notes

• event_type is added or deleted.
• Only events within your plan’s history are returned. If the domain’s TLD is not in your plan, the API answers 403.
• A domain with no events returns records: 0 and an empty data.

GET /v1/keywords

Counts how many added or deleted domains contain each keyword: at the start of the name, at the end, in the middle or anywhere. It counts non-IDN domains only.

Parameters

Example

curl -G -H "Authorization: Bearer $KEY" \
  --data-urlencode "kw=bank|insurance" \
  --data-urlencode "dm=data" \
  --data-urlencode "source=added" \
  "https://api.cifradia.com/v1/keywords"

Response

{
  "status": true,
  "date": "2026-01-15",
  "records": 2,
  "data": [
    {
      "keyword": "bank",
      "tld": "com",
      "domains_starting_with_word": 12,
      "domains_ending_with_word": 5,
      "domains_with_word_in_middle": 3,
      "domains_containing_word_anywhere": 20
    },
    {
      "keyword": "insurance",
      "tld": "com",
      "domains_starting_with_word": 8,
      "domains_ending_with_word": 2,
      "domains_with_word_in_middle": 1,
      "domains_containing_word_anywhere": 11
    }
  ]
}

Notes

• Rows are ordered from most to fewest domains containing the word (domains_containing_word_anywhere).
• With dm=stats the response has status, date and records, without data. With dm=aggregate, data has a single row and no tld.
• domains_containing_word_anywhere counts every domain that contains the word, wherever it is. A name that both starts and ends with it counts in both position counters.

GET /v1/dailyzip/

Downloads a ZIP with every domain added or deleted on one day, one full name per line, in a text file. It is meant for whoever needs the whole day without paging.

Parameters

Example

curl -H "Authorization: Bearer $KEY" \
  -o added_20260115.zip \
  "https://api.cifradia.com/v1/dailyzip/?date=20260115&source=added"

Response

added_20260115.zip
└── added_2026-01-15.txt     # one domain per line, for example:
                             #   example.com
                             #   example.net

Notes

• The path has a trailing slash: /v1/dailyzip/.
• It is only in the plans that include it (Pro and Business). On Starter the API answers 403.
• The file is generated while it downloads, so its size is not known in advance. It respects your plan’s history and includes only the TLDs your plan allows.