Ablecity Manse-force API Reference

The product introduction is document v5.0. Actual API URLs remain under the existing /api/v2/ paths; the document version is separate from the API version.

Developer documentation for integrating Manse-force, Saju, compatibility, naming and visual fortune APIs into apps and web services. This page explains authentication, request parameters, JSON response structure, v2 add-on APIs, callback flows, error codes, rate limits and API key onboarding.

200+ counts paying customers with active monthly subscriptions; test-key users are excluded. UptimeRobot-monitored endpoints recorded uninterrupted uptime during the monitored period since the December 2025 launch. Zero critical errors refers to internal operational records for that period. Availability, support hours and incident response scope are defined in the contract-specific SLA.

Quick Start

Make the first successful call in five minutes

Start with a server-side API key, call the base Manse-force endpoint with GET, then use POST + callback for long-running analysis such as compatibility, naming or yearly wealth/love readings.

Base Manse-force lookup

curl -X GET \
  "https://api.ablecity.kr/api/v2/saju/fortune?birth=1990-01-01T01:00:00&gender=male&city=Seoul&calendar=solar&midnightType=0" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Accept: application/json"

1. Authentication

All requests must include a Bearer token in the HTTP header. Keep keys server-side, avoid embedding them in client apps, and rotate keys when integration ownership changes.

Authorization: Bearer <API_KEY>

2. Common response format

Every endpoint returns a REST JSON envelope. Error responses keep the same top-level shape so client code can handle success and failure consistently.

{
  "status": "success",
  "message": "Request completed.",
  "data": {}
}

3. Operations

Ablecity API is designed for service integration, not only one-off calculation. Authentication, usage management, billing scope, monitoring and SLA options are considered together during onboarding.

Calculates the public v2 Manse-force payload from birth datetime, gender, optional city, midnight handling and calendar type. Public fields cover Four Pillars chart data, five elements, major cycle data, zodiac compatibility, void branches and approved SIS-related structures when enabled for the key.

Manse-force Core (Four Pillars/Saju Data) returns calculation data: chart, Five Elements, Ten Gods, Twelve Stages and major luck cycles. Professional Manse-force + SIS adds strength, chart pattern, favourable elements, branch relationships, void branches and position, status and impact data for 54 Shinsal indicators.

Both products use the existing GET /api/v2/saju/fortune endpoint; API key permissions determine the available scope. The combined field reference and response examples below describe approved permissions and do not mean every professional field is included in Core. SIS intensity is an internal relative index, not a statistical probability.

Code examples

curl -X GET \
  "https://api.ablecity.kr/api/v2/saju/fortune?birth=1990-01-01T01:00:00&gender=male&city=Seoul&calendar=solar&midnightType=0" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Accept: application/json"

import requests

url = "https://api.ablecity.kr/api/v2/saju/fortune"
params = {
    "birth": "1990-01-01T01:00:00",
    "gender": "male",
    "city": "Seoul",
    "calendar": "solar",
    "midnightType": 0,
}
headers = {"Authorization": "Bearer <API_KEY>"}
print(requests.get(url, params=params, headers=headers).json())

const axios = require("axios");

const res = await axios.get("https://api.ablecity.kr/api/v2/saju/fortune", {
  params: {
    birth: "1990-01-01T01:00:00",
    gender: "male",
    city: "Seoul",
    calendar: "solar",
    midnightType: 0
  },
  headers: { Authorization: "Bearer <API_KEY>" }
});
console.log(res.data);

OkHttpClient client = new OkHttpClient();

HttpUrl url = HttpUrl.parse("https://api.ablecity.kr/api/v2/saju/fortune").newBuilder()
    .addQueryParameter("birth", "1990-01-01T01:00:00")
    .addQueryParameter("gender", "male")
    .addQueryParameter("city", "Seoul")
    .addQueryParameter("calendar", "solar")
    .addQueryParameter("midnightType", "0")
    .build();

Request request = new Request.Builder()
    .url(url)
    .addHeader("Authorization", "Bearer <API_KEY>")
    .build();

Query parameters

5. Public response fields

The response exposes integration-facing fields. Internal scoring logic, private rule tables and debug fields are not included in public documentation.

{
  "status": "success",
  "message": "Request completed.",
  "data": {
    "saju": {
      "year": { "heaven": "庚", "earth": "午" },
      "month": { "heaven": "戊", "earth": "子" },
      "day": { "heaven": "丙", "earth": "寅" },
      "hour": { "heaven": "己", "earth": "丑" }
    },
    "five_elements": { "wood": 2, "fire": 2, "earth": 2, "metal": 1, "water": 1 },
    "ten_gods": [],
    "daeun": [],
    "gongmang": [],
    "zodiac_compat": [],
    "sinsal": []
  }
}

6. v2 add-ons and analysis APIs

In addition to the base Manse-force lookup, v2 provides daily luck, luck-flow and deeper analysis modules. Endpoints under fortune/request-analysis/ use POST + callback.

9. Error codes

10. Rate limit

To keep the production service stable, request volume is limited per issued API key. Higher limits can be discussed based on business volume and contract scope.

The request frequency limits below are separate from the total Sandbox allowance. Products and limits follow the approved scope of the issued key.

11. FAQ

12. Support

Before integration, contact us by email. After key issuance, use the API Dashboard for usage, subscription and API lookup checks.

Operating conditions to confirm before integration

Review expected volume, response fields and error handling with samples, including callback receipt, deduplication and retries. Key permissions, support hours, incident response, data retention/deletion and version-change notices are defined during technical review and contracting.