openephemeris-com · Schema

ChineseCalendarConvertResponse

CompanyAstrologyArtificial IntelligenceAstronomyData

Properties

Name Type Description
day object One day of the Chinese calendar. date (Gregorian), weekday_iso (1 Monday .. 7 Sunday); lunar {year, month, day, leap, month_days, month_name, day_name, year_ganzhi (the lunar year's name, New Year bou
jie_in_force object The month-opening term (节) whose date is on or before this date: the term that set the month pillar. {id, names, kind, longitude, instant, date}.
metadata object Provenance: calendar (chinese_lunisolar_dingqi), meridian (Beijing local mean time UTC+7:45:40 before 1929, UTC+8 from 1929), timezone, ephemeris, rules (month start, month 11, leap month, a new moon
next_solar_term object The first solar term dated after this date, {id, names, kind, longitude, instant, date}.
success boolean
timezone string The IANA zone every instant and hour is given in.
View JSON Schema on GitHub

JSON Schema

openephemeris-com-chinese-calendar-convert-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/openephemeris-com/json-schema/openephemeris-com-chinese-calendar-convert-response-schema.json",
  "title": "ChineseCalendarConvertResponse",
  "x-generated": "2026-11-10",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/openephemeris-com-chinese-api-openapi.yml#/components/schemas/ChineseCalendarConvertResponse",
  "additionalProperties": true,
  "properties": {
    "day": {
      "additionalProperties": true,
      "description": "One day of the Chinese calendar. date (Gregorian), weekday_iso (1 Monday .. 7 Sunday); lunar {year, month, day, leap, month_days, month_name, day_name, year_ganzhi (the lunar year's name, New Year boundary), zodiac, boundary_margin_seconds, boundary_warning (the new moon that fixes this month's first day is within 300 s of Beijing midnight, so a table may number the day one off)}; pillars {year (Lichun boundary), month (jie boundary), day}, each a sexagenary pair {id, index 1-60, stem, branch, name_zh, name_zh_hant, name_pinyin}; solar_terms (the terms on this date, each {id, names, kind jie|zhongqi, longitude, instant}); tong_shu {officer (建除十二神), xiu (the 28-lodge day cycle with full name and luminary), clash {ganzhi, branch, zodiac}, sha_direction}; natal_clashes when natal_pillars was sent; hours (convert only): the 12 two-hour pillars from the Zi hour at 23:00 of the previous day, each {branch, ganzhi, start, end}. Names: id (stable ASCII id, localise from it), name_zh (simplified Chinese), name_zh_hant (traditional), name_pinyin (Hanyu Pinyin with tone marks).",
      "type": "object"
    },
    "jie_in_force": {
      "additionalProperties": true,
      "description": "The month-opening term (节) whose date is on or before this date: the term that set the month pillar. {id, names, kind, longitude, instant, date}.",
      "type": "object"
    },
    "metadata": {
      "additionalProperties": true,
      "description": "Provenance: calendar (chinese_lunisolar_dingqi), meridian (Beijing local mean time UTC+7:45:40 before 1929, UTC+8 from 1929), timezone, ephemeris, rules (month start, month 11, leap month, a new moon and a solar term on the same date, the pillar boundaries, the lodge cycle, hours, clash, sha), range, accuracy (the honest limits: a computed calendar, not the almanac the Qing court issued; the few Hong Kong Observatory disagreements; Delta T toward 2650). In llm mode on the almanac also days and days_schema.",
      "type": "object"
    },
    "next_solar_term": {
      "additionalProperties": true,
      "description": "The first solar term dated after this date, {id, names, kind, longitude, instant, date}.",
      "type": "object"
    },
    "success": {
      "type": "boolean"
    },
    "timezone": {
      "description": "The IANA zone every instant and hour is given in.",
      "type": "string"
    }
  },
  "type": "object"
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/openephemeris-com-chinese-calendar-convert-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.