Integration guide

To call the Open API, create an app and get a Client ID and Client Secret.

Create an app

1. App screen Fill out the application form.
2. Enter service name, English name (channel code), and service URL, then submit.
3. After ops review, a private channel is created and you'll get the result by email. Once approved, create API keys on the app detail page.

Issue API client

1. App details On the API client section, [Add client] click
2. Enter Client ID (free, up to 100 chars) and select scopes.
3. Shown immediately after creation Save the Client Secret immediately in a safe place This value won't be shown again.

Scopes

• buildingUnit:readBUILDING_UNIT_READView rooms
• buildingUnit:writeBUILDING_UNIT_WRITECreate/Edit room mapping
• booking:readBOOKING_READView bookings
• booking:writeBOOKING_WRITECreate/Edit bookings
• contract:readCONTRACT_READView contracts
• contract:writeCONTRACT_WRITECreate/Edit contracts (Method B)
• user:writeUSER_WRITECreate users (Method A · login integration)
• userLoginTicket:writeUSER_LOGIN_TICKET_WRITEIssue login ticket (Method A · login integration)
• chat:readCHAT_READView chats
• chat:writeCHAT_WRITECreate/Send chats

To register contracts/reservations via API, create a test room and set channel mapping.

Procedure

1. Host screen Register a new room.
2. Channel mapping screen Select the registered room and set room-level and unit-level mappings. Room-level mapping is optional, but unit-level mapping is required to register contracts via the Open API. Set the external property ID to the room ID used by that channel.
3. To view the registered room on the guest page, /rooms/{roomId}visit the guest page.

Register plott LIFE Open API's MCP server with AI coding agents (Claude Code, Cursor, etc.) so agents can read the API spec immediately and speed up integration.

Register with Claude Code

claude mcp add --transport http plott-life-partner \
  https://life.plott.co.kr/api/open/mcp \
  --header "Authorization: Basic {base64(clientId:clientSecret)}"

{base64(clientId:clientSecret)} is the Client ID and Secret issued in Step 01 clientId:clientSecret concatenated with a colon and base64-encoded.

Two integration methods depending on how much your service handles Method A · Login integration One is the handoff method: integrate only listings and login, handing off contracts/payments to plott LIFE, Method B · Contract integration the other integrates contract APIs so sales finish inside the partner app. Select a tab below to view its implementation and operation steps.

const res = await fetch(
  'https://life.plott.co.kr/api/open/v1/building-unit-type?page=0&size=20&operationStatus=PUBLISHED',
  { headers: { Authorization: `Basic ${credentials}` } },
);
const { items, totalItems, totalPages } = await res.json();

const res = await fetch('https://life.plott.co.kr/api/open/v1/user', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Basic ${credentials}`,
  },
  body: JSON.stringify({
    externalUserId: 'partner-user-001',
    email: 'user@example.com',
    firstName: '길동',
    lastName: '홍',
    phoneCode: '82',
    phoneNumber: '1012345678',
    countryCode: 'KR',
  }),
});

const { id } = await res.json(); // 플라트라이프 회원 ID

const res = await fetch(
  'https://life.plott.co.kr/api/open/v1/userLoginTicket',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: `Basic ${credentials}`,
    },
    body: JSON.stringify({ externalUserId: 'partner-user-001' }),
  },
);

const { ticket } = await res.json(); // 5분 TTL · 1회용

If integration is verified in a private channel, request public channel access to reach all hosts' listings. This step is the same for both methods.

How to request

1. App details On the app's status card [Request public channel access] Click it.
2. Our operations team will review and email the result.
3. If rejected, check the reason, fix the issue, and reapply.

When public, you can query all plott LIFE hosts' listings via Open API. Pick listings to handle, set channel mapping, and operate using your chosen integration flow.

View all listings

const res = await fetch(
  'https://life.plott.co.kr/api/open/v1/building-unit-type?page=0&size=20',
  { headers: { Authorization: `Basic ${credentials}` } },
);
const { items, totalItems, totalPages } = await res.json();

All Open API requests use HTTP Basic auth. App details obtained from Client ID and Client Secret join with a colon and encode in base64 Authorization include it in the header.

const credentials = Buffer.from(
  `${process.env.CLIENT_ID}:${process.env.CLIENT_SECRET}`,
).toString('base64');

const res = await fetch('https://life.plott.co.kr/api/open/v1/contract-channel', {
  headers: {
    Authorization: `Basic ${credentials}`,
  },
});

When an error occurs, RFC 9457 Problem Detail it responds in the following format.

{
  "type": "about:blank",
  "title": "Not Found",
  "status": 404,
  "detail": "예약 매핑을 찾을 수 없습니다.",
  "instance": "/open/v1/booking"
}

• typeError type URI
• titleHTTP status text
• statusHTTP status code
• detailError detail
• instanceRequest path

To ensure stability and fair use, the Open API enforces rate limits.

• ScopeAll endpoints under /open/**
• Limit unitHost account
• Limit300 requests per minute
• Refill methodGreedy refill: ~5 tokens refilled every second.

Rate-limit exceeded response

Requests exceeding the limit are rejected immediately, 429 Too Many Requests and an error response is returned.

Recommended client handling

• 429 When you receive the response, do not retry immediately, wait a while before retrying.
• On average about 200ms intervals is stable.
• For batch jobs needing many requests quickly, space calls or use exponential backoff.