Nameday Abalin Nameday API

Name: Nameday API
Brand: Nameday API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationnone3 EndpointsREST

For Agents

Look up name days for a person's name or fetch today's namedays across European country calendars. Read-only, no auth.

Install Jentic One Beta

Connect the Nameday API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nameday API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnameday.abalin.net%2Fnameday-abalin" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnameday.abalin.net%2Fnameday-abalin" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Nameday API.

Retrieve today's namedays for one or many countries in a single request

Fetch all namedays falling on a specific calendar date across supported countries

Search the date associated with a given first name in a country's nameday calendar

GET STARTED

Start building with Nameday API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Nameday API for, with concrete tasks.

★ Personalised Greeting Automation

Many Central and Eastern European cultures celebrate name days alongside birthdays. Apps that send automated greetings call the today endpoint each morning, match the returned names against a contact list, and trigger personalised emails or SMS. The integration takes minutes because no authentication is required and responses are small JSON payloads.

Call GET /V2/today/Europe%2FPrague and email any contact whose first name appears in the Czech namedays list.

Nameday Lookup in Multilingual Apps

Localised calendar apps display the nameday for the current date alongside holidays. By calling GET /V2/date for a given month and day, the app gets parallel nameday entries for every supported country, letting users see what their name corresponds to in another locale. Three endpoints cover the entire feature without needing a custom data set.

Fetch namedays for month=11 day=19 and surface the Hungarian, Polish, and Slovak names side by side in a calendar widget.

Search a Name's Celebration Date

When users want to know when their name is celebrated, the search endpoint takes a first name and country and returns the matching date in the local nameday calendar. This is useful for diaspora communities and travel apps that surface cultural cues to visitors. The POST /V2/getname endpoint accepts a name and country code and returns the day and month of celebration.

POST to /V2/getname with name='Eva' and country='cz' to retrieve the date Eva is celebrated in Czech Republic.

AI Agent Cultural Awareness

An AI assistant invoked through Jentic can answer culturally aware queries like 'is it Karol's name day today in Slovakia?' Because the API needs no auth, the agent calls it through the Jentic SDK with no vault configuration, blending nameday data with calendar reasoning to suggest greetings, social-media posts, or messaging cues for the user.

Search Jentic for 'todays namedays', load the GET /V2/today/{timezone} operation, and execute it for Europe/Bratislava to surface Slovak namedays.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for nameday api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/V2/today/{timezone}

Get today's namedays per country, scoped to a timezone

GET

/V2/date

Get namedays for a specific month and day

POST

/V2/getname

Search for a name's celebration date in a country

GET

/V2/today/{timezone}

Get today's namedays per country, scoped to a timezone

GET

/V2/date

Get namedays for a specific month and day

POST

/V2/getname

Search for a name's celebration date in a country

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

The Nameday API needs no credentials, but wiring it by hand still means building calls against nameday.abalin.net/api and mapping its today, date, and getname endpoints yourself. Through Jentic you install once, import the Nameday API from the API Directory, and your agent calls it with one audited outbound path.

Permission scoping

The Nameday API passes the timezone and name through request parameters and bodies rather than a resource id in the URL path, so scope the agent to the operations it needs, such as reading today's namedays or searching by name, and leave any others out of the allowed set unless you include them.

Credential isolation

The Nameday API has no credentials to store, so there is no secret to manage. Requests still run through your own Jentic One instance, which keeps them out of the agent's prompt, logs, and context.

Intent-based discovery

Agents search Jentic by intent such as 'find todays namedays' or 'search a nameday by name', and Jentic returns the matching Nameday operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Nameday API through Jentic.

Why is there no official OpenAPI spec for Nameday API?

Abalin does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nameday API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Nameday API use?

The Nameday API is open and requires no API key, OAuth token, or basic auth. When called through Jentic the agent receives the operation schema and calls the endpoint anonymously, so no vault entry is needed.

Which countries does the Nameday API cover?

The API supports parallel nameday calendars for Czech Republic, Slovakia, Hungary, Poland, Germany, Spain, France, Italy, Croatia, Sweden, Austria, and the United States. Each response from /V2/today and /V2/date contains a per-country namedays object so you can read multiple locales in a single call.

Can I look up the date a specific name is celebrated through the Nameday API?

Yes. POST /V2/getname accepts a name and country code (for example name='Eva', country='cz') and returns the matching month and day from that country's nameday calendar. Use this when users ask 'when is my name day' rather than 'who has a name day today'.

What are the rate limits for the Nameday API?

Abalin does not publish a formal rate limit in the spec. Because nameday data for a given date is stable across years for most countries, agents should cache /V2/today and /V2/date responses for at least 24 hours to avoid hitting the public service unnecessarily.

How do I fetch today's namedays for Slovakia through Jentic?

Run jentic.search('todays namedays by country'), load the GET /V2/today/{timezone} operation, then execute it with timezone='Europe/Bratislava'. The returned JSON contains a 'namedays' object with a 'sk' field listing names celebrated in Slovakia today.

Can I limit what my agent is allowed to do with the Nameday API?

Yes. Because you run Jentic One yourself, your own rules decide which Nameday operations the agent may call, so you can allow only the ones it needs. For example, you can permit reading today's namedays through GET /V2/today/{timezone} or looking up a date with GET /V2/date while leaving the POST /V2/getname name search out of the allowed set. Since this API passes the timezone and name through request parameters and bodies rather than a resource id in the URL path, scoping is done at the operation level by choosing which endpoints the agent is permitted to run.