Skip to content
/bounty
Sign in
All bounties

SKT T world

Open
tworld.co.kr

Unofficial browser-based self-service for SKT mobile and broadband accounts.

Reward
₩500,000
Tier
Platinum
Auth
Browser
APIs
6 APIs
Working now
none
Posted
2026-07-07
Kind
New service
Lifecycle
  1. Open
  2. Claimed
  3. In review
  4. Finalizing
  5. Syncing
  6. Merged
  7. Paid

Scope

Build a browser-facing provider for the SKT T world self-service portal. It should cover current plan and usage review, bill and payment history, comparison of eligible plans and roaming or add-on options, change preparation with fee impact, explicit change confirmation, and follow-up status retrieval. The surface is login-gated and contract-sensitive, with carrier-specific rules and possible step-up verification.

Expected APIs

6
get-current-plan-billing-usage-summaryGet current plan, billing, and usage summaryReadMedium

Retrieve the account's active plan, current bill snapshot, and recent usage counters. This is the starting point for understanding what service the line is on and what it has consumed so far.

Inputs
  • account_idstringOptionalOptional carrier account or subscriber identifier.Example 01012345678
  • billing_cyclestringOptionalOptional billing cycle to inspect, such as the current month or a date bucket.Example 2026-07
  • service_typestringOptionalOptional service filter such as mobile, broadband, or IPTV.Example mobile
Outputs
plan_namebilling_amountusage_datausage_voiceusage_sms
Acceptance
  • Returns the current plan alongside bill and usage figures for the requested account scope.
  • Separates data, voice, and SMS usage when the carrier exposes those counters.
  • Does not imply account changes or service actions from this read-only summary.

Auth required for this API.

compare-eligible-plans-addons-roaming-optionsCompare eligible plans, add-ons, and roaming optionsReadMedium

Look up what plans, add-ons, or roaming bundles the account can move to. The result should expose carrier restrictions, eligibility, and the key differences that matter before starting any change request.

Inputs
  • service_typestringOptionalMobile, broadband, or another carrier service category.Example mobile
  • target_countrystringOptionalOptional roaming destination for travel bundles.Example JP
  • plan_namestringOptionalOptional current or target plan name to compare against.Example 5G 프라임
Outputs
eligible_planseligible_addonsroaming_optionseligibility_notes
Acceptance
  • Returns only options the account is allowed to consider or purchase.
  • Highlights roaming or add-on alternatives with the relevant eligibility notes.
  • Preserves plan differences rather than flattening them into a generic catalog.

Auth required for this API.

prepare-plan-addon-change-fee-impactPrepare plan or add-on change with fee impactWriteHard

Stage a plan, add-on, or roaming change and show the financial impact before commitment. The preview should include prorated fees, contract extensions, device subsidy effects, and any penalty or discount that the carrier would apply.

Inputs
  • account_idstringRequiredSubscriber or account identifier for the carrier line.Example 01012345678
  • target_product_idstringRequiredPlan, add-on, or roaming product identifier to stage.Example PLAN-5G-PRIME
  • effective_datedateOptionalRequested date the change should take effect.Example 2026-08-01
Outputs
change_draft_idfee_impacteffective_datecontract_impacteligibility_notes
Acceptance
  • Shows the expected fee or pro-rating impact before the carrier change is committed.
  • Includes contract or subsidy effects that could change the user's obligations.
  • Rejects requests that are not eligible for the selected account or service line.

Auth required for this API.

confirm-user-approved-change-requestConfirm a user-approved change requestWriteHard

Submit the staged carrier change only after the user explicitly approves the exact product and fee impact. This is the irreversible request step for plan, add-on, or roaming adjustments and should not run without a confirmation gate.

Inputs
  • change_draft_idstringRequiredDraft created by the change-preparation step.Example CHG-88440
  • user_confirmationbooleanRequiredExplicit user approval to commit the change.Example true
  • payment_method_idstringOptionalOptional payment method reference if an upfront fee must be charged.Example CARD-1
Outputs
change_request_idrequest_statuseffective_datereceipt_numberfee_charged
Acceptance
  • Requires a positive explicit confirmation before submission.
  • Returns a request identifier and status for the committed carrier change.
  • Fails safely if the draft has expired or the account loses eligibility.

Auth required for this API.

list-bills-payments-contract-commitmentsList bills, payments, and contract commitmentsReadMedium

Retrieve invoice history, payment records, and any remaining contract obligations on the line. This is useful for checking whether a plan change will trigger a fee or whether the billing history matches the user's expectations.

Inputs
  • billing_cyclestringOptionalOptional cycle or month to inspect.Example 2026-07
  • account_idstringOptionalOptional account identifier for the subscriber line.Example 01012345678
Outputs
invoice_nopayment_statusdue_amountcontract_end_datepenalty_amount
Acceptance
  • Returns invoices or payment rows for the requested billing scope.
  • Includes any remaining contract commitment or penalty information when available.
  • Supports looking up a single account without mixing unrelated subscriber records.

Auth required for this API.

get-change-roaming-support-request-statusGet change, roaming, or support-request statusReadMedium

Check the current state of a submitted plan change, roaming order, or support request. Users need this to verify whether a carrier action is pending, completed, rejected, or still waiting on verification.

Inputs
  • request_idstringRequiredIdentifier for the change, roaming, or support request.Example CHG-88440
  • request_typestringOptionalOptional type hint such as change, roaming, or support.Example change
Outputs
request_idrequest_statussubmitted_atupdated_atnext_action
Acceptance
  • Returns the latest lifecycle state for the specified carrier request.
  • Includes a next-action hint when the request still needs user or carrier follow-up.
  • Keeps request-type context when it matters for the returned status.

Auth required for this API.

Suggested surface. Propose changes in your submission if the upstream differs.

Acceptance criteria

  • Service scaffolded from the public @apifuse/provider-sdk
  • All listed APIs implemented with Zod/Standard Schema input & output
  • Each API declares exactly one of healthCheck or healthCheckUnsupported
  • Real upstream fixture data included where applicable
  • bun run check and bun run test pass
  • Auth, credential and env-secret behavior documented. No real secrets committed

Evidence to submit

  • Workspace repository and main commit link
  • SDK version/tag and the create command used
  • API list with input/output summaries
  • healthCheck coverage table per API
  • bun run check and bun run test output

Ready to claim?

Submit a claim. Your workspace is prepared after confirmation.