ApiFuseApiFuse

Public changelog

ApiFuse changes customers should know about

Public API, provider operation, lifecycle, and migration updates are listed here from the validated ApiFuse changelog source.

Browse API reference

Generated from OpenSpec changelog entries at 2026-05-26T08:01:17.000Z.

  1. PatchShipped

    The legacy `ohouse-deals/today_deals` alias now has a unique MCP tool-router name so it no longer collides with the canonical `ohouse-deals/today-deals` operation.

    The operation API path and response contract are unchanged. This only disambiguates the generated MCP/developer metadata for the legacy alias.

    Affected surface
    ohouse-deals/today_deals
    Action required
    No
    Migration guidance
    No client migration is required. API callers continue to use `/v1/ohouse-deals/today_deals`; MCP clients should discover the regenerated tool metadata instead of hard-coding sanitized names.
  2. BreakingShipped

    Ohouse expands from Today Deals-only extraction into a Daiso-style public read provider covering commerce, content, metadata, reviews, Q&A, promotions, and comments.

    The Ohouse provider now uses HAR and live browser-TLS evidence to expose stable public `/api` and `/apig` surfaces instead of relying only on recursive SSR payload extraction. New read-only operations cover product search/category/detail, product options, delivery, reviews, questions, recommendations, deal products, coupon display metadata, exhibitions, navigation metadata, search trends, promotion cards, content cards, product-used cards, project detail/recommendations, card collection recommendations, and public comments. Volatile Next.js build-data URLs and analytics or user mutation endpoints are cataloged in source but are not exposed as customer operations.

    Affected surface
    ohouse-deals/today-deals, ohouse-deals/today_deals, ohouse-deals/search_products, ohouse-deals/browse_store_category, ohouse-deals/browse_product_categories, ohouse-deals/get_product_detail, ohouse-deals/get_products_by_ids, ohouse-deals/get_product_options, ohouse-deals/get_product_delivery, ohouse-deals/get_product_reviews, ohouse-deals/get_product_questions, ohouse-deals/get_product_recommendations, ohouse-deals/get_deal_products, ohouse-deals/get_product_coupons, ohouse-deals/get_exhibition_section_items, ohouse-deals/get_site_metadata, ohouse-deals/get_search_trends, ohouse-deals/get_promotions, ohouse-deals/search_cards, ohouse-deals/get_product_used_cards, ohouse-deals/get_project_detail, ohouse-deals/get_project_recommendations, ohouse-deals/get_card_collection_recommendations, ohouse-deals/get_comments
    Action required
    Yes
    Migration guidance
    Existing `ohouse-deals/today-deals` callers should regression-test strict response-schema assumptions because the operation now prefers the stable feed API, returns stronger product identifiers when upstream exposes them, and adds source API metadata. Callers that only read prior deal fields such as title, brand, URL, price, discounts, reviews, free_delivery, sold_out, and source_url remain supported. New operations are additive.
  3. BreakingShipped

    Provider temporal and closed-option inputs now reject ambiguous free-form strings at schema validation time instead of letting malformed values reach upstream APIs.

    This narrows public provider input schemas for date, time, datetime, and finite routing-option fields so agent/tool layers fail fast before dispatching ambiguous temporal values or unsupported options to upstream services. Existing clients that already send the documented formats continue to work; clients relying on loose strings should normalize before calling the operation.

    Affected surface
    catchtable/availability, catchtable/reserve, kakaomap-api/car-directions, kakaomap-api/transit-directions, kma-forecast/mid-forecast, kma-forecast/short-forecast, kma-forecast/weather-by-address, modu-parking/start-payment, naver-flight/search-flights, naver-flight/search-oneway-flights, naver-map-api/transit-directions
    Action required
    Yes
    Migration guidance
    Update callers to send exact documented wire formats. CatchTable reservation dates and returned availability date_slots use YYYY-MM-DD, and reservation times use HH:MM such as 19:00, not 1900 or 7pm. KakaoMap transit times and KMA base times must use compact HHmm. Naver Map and Modu Parking prediction datetimes must include an ISO 8601 timezone. Naver Flight dates must use YYYY-MM-DD. KakaoMap car priority and transit sort must use the documented enum values.
  4. BreakingShipped

    Daiso now uses the renewed mall fapi contract and adds grouped product, review, store, inventory, catalog, recommendation, metadata, and promotion operations.

    The Daiso provider has moved from the retired mall website API path to the renewed `fapi.daisomall.co.kr` and current mall read endpoints captured from the renewal HAR. The existing `daiso-api/products` operation remains available but now resolves product discovery through the renewed FindStoreGoods flow, so customers should regression-test any strict response-shape assumptions. New grouped operations expose detail, reviews, store lookup, pickup inventory, product availability, catalog, trend, recommendation, metadata, and promotion surfaces while preserving sanitized source-payload coverage and partial-failure metadata.

    Affected surface
    daiso-api/products, daiso-api/search_products, daiso-api/get_product_detail, daiso-api/get_product_reviews, daiso-api/search_stores, daiso-api/get_store_inventory
    Action required
    Yes
    Migration guidance
    Existing daiso-api/products callers should verify response mappings against the renewed FindStoreGoods-backed schema and prefer the new grouped operations when they need details, reviews, stores, inventory, or catalog fanout.
  5. BreakingShipped

    KakaoMap transit info now publishes explicit branch schemas, and Law compare now exposes evidence-backed envelope fields instead of guessed normalized rows.

    ApiFuse now removes the remaining unknown response-schema fields from provider API docs without inventing upstream contracts. `kakaomap-api/transit-info` exposes explicit bus stop, bus line, and subway station response branches. `law-service/compare` no longer returns guessed normalized comparison rows. It exposes documented law.go.kr list envelope metadata (`summary`), the actual upstream target/format, unmodified upstream scalar row fields for `oldAndNew` and `thdCmp`, and raw HTML for the documented HTML-only `lsHistory` branch.

    Affected surface
    kakaomap-api/transit-info, law-service/compare
    Action required
    Yes
    Migration guidance
    KakaoMap transit-info callers should read the documented bus-stop, bus-line, or subway-station branch fields under info instead of relying on arbitrary upstream raw fields. Law compare callers must migrate from comparison.items/comparison.total to summary/items/html. The law-service compare items are unmodified upstream row objects; only summary fields are normalized because they are documented by law.go.kr list guides. The legacy lsHstInf input now calls the documented lsHistory HTML target and returns raw_format=html with html content.
  6. BreakingShipped

    Provider schemas now reject unsupported closed-domain strings instead of accepting broad string values.

    ApiFuse now models known finite provider contract values as enums or standard-code patterns rather than accepting arbitrary strings. This makes OpenAPI output and SDK-generated clients fail fast for unsupported values such as unknown payment gateways, typoed sort options, or invalid result/status codes. The affected operations keep their existing runtime behavior for valid callers. Clients that were sending out-of-contract values should migrate to the documented enums shown in the operation schema. Fields that are intentionally upstream-extensible, such as map category taxonomies or CMS section types, remain open strings and are documented as open-world values instead of being narrowed prematurely.

    Affected surface
    catchtable/reserve, catchtable/cancel-reservation, catchtable/register-waiting, catchtable/cancel-waiting, delivery-api/carriers, law-service/search, law-service/compare, yogiyo-api/find-restaurants, yogiyo-api/place-order
    Action required
    Yes
    Migration guidance
    Update callers to send only documented enum values for closed domains. Yogiyo search sort must be one of recommended, rating, distance, delivery_fee, or delivery_time; Yogiyo place-order reports NAVER_PAY as the payment gateway; Law compare_type must be oldAndNew, thdCmp, or lsHstInf; Law search result type is law, prec, terms, or other; Catchtable action-result statuses are the documented successful terminal status for that action; Delivery carrier country codes are lowercase ISO 3166-1 alpha-2 values.
  7. BreakingShipped

    Modu Parking start-payment now exposes the shared-parking payment fields and can create NaverPay and NicePay URLs from one verified SMS session.

    `modu-parking/start-payment` now aligns its shared-parking payment WebView request with the current Modu Parking webapp contract. The operation accepts optional shared-payment amount fields (`price`, `point`, `total_price`) plus `car_number` and maps them to the upstream `carNum`, `price`, `point`, `totalPrice`, `platform`, and `authCodeSeq` payload. This is primarily an enablement change for real-SMS health journeys and shared-parking payment URL creation. Existing clients are not forced to migrate immediately, but shared-parking payment flows should pass the price returned by `check-availability` and a valid vehicle number for reliable payment URL generation. When `pg_types` is `["naverpay","nicepay"]`, `start-payment` verifies the SMS code once, obtains the upstream guest session once, then creates both NaverPay and NicePay WebView URLs. The primary `payment_url` follows `pg_type`, and `payment_urls.naverpay` / `payment_urls.nicepay` exposes the PG-specific URLs.

    Affected surface
    modu-parking/start-payment
    Action required
    No
    Migration guidance
    Existing ticket_id and share_seq callers can continue using the operation. Shared-parking callers may now pass price, point, total_price, and car_number from check-availability/user input so the provider can create the payment WebView URL against the current Modu Parking contract. Set pg_types to ["naverpay","nicepay"] when both NaverPay and NicePay URLs are needed after a single SMS verification; keep pg_type as the primary gateway.
  8. BreakingShipped

    Adds Korean commerce public read providers and restores Daiso pickup inventory with a normalized stock contract.

    ApiFuse now exposes additional public, read-only Korean commerce providers for Market Kurly product lookup, Daangn public listings, Danawa product and price comparison, and Ohouse Today Deals discovery. Daiso inventory is no longer modeled as an unsupported legacy lookup: it performs the current non-login pickup-stock ceremony and returns explicit store stock state instead of relying on request success as availability. The only compatibility-impacting existing public operation is `daiso-api/inventory`. Clients that consumed the previous unsupported shape should read `retrieval_status` and per-store stock fields from the new normalized response. All other operations listed here are newly added public provider operations.

    Affected surface
    daiso-api/inventory, market-kurly/search-products, market-kurly/count-products, market-kurly/product-detail, daangn-marketplace/used-goods-search, daangn-marketplace/used-goods-detail, daangn-marketplace/realty-search, daangn-marketplace/realty-detail, daangn-marketplace/jobs-search, daangn-marketplace/jobs-detail, daangn-marketplace/cars-search, daangn-marketplace/cars-detail, danawa-price/search-products, danawa-price/get-offers, danawa-price/compare-products, ohouse-deals/today-deals
    Action required
    Yes
    Migration guidance
    Daiso inventory callers should migrate from the previous unsupported inventory response contract to the new pickup-stock response fields: selected_store, retrieval_status, stores[].in_stock, stores[].quantity, and stores[].inventory_label. New Market Kurly, Daangn, Danawa, and Ohouse operations are additive public read tools and require no migration.
  9. BreakingShipped

    CatchTable public read operations no longer require a user-owned connection reference.

    CatchTable search, restaurant detail, reviews, reservation availability lookup, and waiting information are now modeled as public read tools in the ApiFuse MCP and OpenAPI contracts. Agents can discover and call these operations without asking users for a connected CatchTable account. Customer-owned account references remain required for actions that inspect or mutate a user's own reservations, waitings, or bookings.

    Affected surface
    catchtable/search, catchtable/shop, catchtable/reviews, catchtable/availability, catchtable/waiting-info
    Action required
    No
    Migration guidance
    Remove externalRef from these read-only calls if your client was sending one only to satisfy the old schema. Booking, cancellation, waiting registration, and user status calls still require a connection reference.
  10. AddedPre-GA

    ApiFuse now publishes a public changelog and operation contract baseline before launch.

    ApiFuse now tracks provider operation contract versions, compatibility hashes, and customer-visible changelog entries before general availability. Existing provider operations start at contract version `1.0.0`; no customer migration is required for this pre-GA baseline.

    Affected surface
    platform-docs, provider-operations
    Action required
    No
    Migration guidance
    none