Holiday information
Return planned date and holiday information in a consistent shape, with the applicable calendar rule visible in the documentation.
KOREAPIS
Calendar rules developers should not rebuild every time.
A planned developer API for Korean public holidays and business-day calculations with clear JSON and error contracts.
MVP planning · Preparing to build
Planned API surface
Date rules expressed as a stable API contract.
The MVP is being designed around predictable requests, explicit date rules, and responses an application can use without reimplementing calendar logic.
- 01 · RequestA date range, locale, and business-day rule
- 02 · ResolveHoliday and working-day logic under versioned rules
- 03 · ValidateExplicit parameters and error responses
- 04 · ReturnJSON suitable for service scheduling and forms
Small API surfaces, explicit rules
The first proposed scope focuses on the calendar logic that repeatedly appears in Korean service development.
Business-day calculation
Calculate a next or previous business day from a date and a specified direction. Boundary cases are part of the contract design.
Predictable integration
JSON responses and error behavior are being designed together. API keys and quota controls are design topics, not a currently available service.
A clear delivery flow
The interface is planned around explicit inputs, deterministic rules, and documented responses.
-
01
State the date question
Choose a date, calculation direction, and requested result.
-
02
Apply verified rules
Use deterministic calendar and holiday rules for the core calculation.
-
03
Receive a contract response
Read the result or a documented error code.
Proposed interface, not a live endpoint
GET /v1/business-days/next?date={input-date}
200 { "date": "{calculated-date}" }
Errors will use a documented JSON contract.
Claude for clearer integration guidance
The core date calculation remains rule based and testable. Any Claude-assisted guidance is a later possibility, after Findoc’s planned API evaluation.
Current: planning with Codex
Codex supports requirement clarification, contract drafts, and boundary-value test design while the founder reviews the resulting decisions. Claude Code is being evaluated for selected development workflows.
Planned: integration guidance
After Findoc’s planned API evaluation and once this API is built, we may assess sending a developer’s question, sanitized error code, and public specification to Claude. The output would explain a correction with a relevant code example.
Check the guidance against the source
Guidance would link to the relevant specification and ask developers to test suggested code. Date results would continue to come from tested API rules. We would evaluate specification accuracy and whether examples run correctly.
Questions
Is the API available now?
No. KoreAPIs is in MVP planning and preparing to build; the example interface is not a live endpoint.
How will correctness be checked?
The plan includes contract and boundary-value tests for calendar rules, then review of documentation and any optional explanatory AI output.
Product conversation