Service
Get municipal guidance on when, where, and how to dispose of household waste, food waste, recyclables, and bulk waste for Korean districts.
96.53%30-day uptimeAvg response331ms
Selecting a row opens the reference for that API.
| Method | API | Path | Summary |
|---|---|---|---|
| POST | /v1/korea-mois-household-waste/dataset-source | Returns the official data.go.kr file dataset (행정안전부_생활쓰레기배출정보) that is the source of record for the household waste guidance, after confirming its dataset page is still published. Use when you need to cite or verify the upstream dataset behind the guidance. Do NOT use for collection schedules or disposal rules — use korea-mois-household-waste:waste-collection-schedules instead. Takes no input. Returns title, source_url and note. | |
| POST | /v1/korea-mois-household-waste/waste-collection-schedules | Looks up official municipal household waste collection schedules and disposal rules for a Korean district (시군구). Use when a user asks when, where, or how to dispose of general household waste, food waste, recyclables, or bulk waste in a specific district — pass the district name in Korean (e.g. 강남구) as district_name; it is matched as a partial (LIKE) filter on the upstream district name, so a short name can match many management zones. Use page and limit to walk them: summary.total_count reports how many matched in total and summary.has_more reports whether any remain after this page. Do NOT use to cite or verify the upstream dataset itself — use korea-mois-household-waste:dataset-source instead. Returns query.district_name, summary (page, limit, returned_count, total_count, has_more) and items[] of per-management-zone guidance (province, city, zone_name, zone_areas, management department with phone_e164, general_waste/food_waste/recyclable schedules with collection_days, start_time, end_time and method, bulk_waste window and location, no_collection_days) for the agent to summarize. |
Issue a sandbox key and make your first reservation.
APIFuse holds the partner credentials. You hold one managed key.
Receive events such as reservation confirmations and delivery updates.
Service outages and gateway errors normalise into one error model.
