Skip to content
/bounty
Sign in
All bounties

Gov24

Open
gov.kr

Korean government civil-service workflows for certificates, applications, status checks, and document downloads.

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

This provider covers browser-based Gov24 flows. It is a high-trust, unofficial automation target with login, identity verification, document collection, application preparation, explicit submission approval, status tracking, and issued-document download requirements. Implementations must avoid exposing PII in logs or summaries.

Expected APIs

6
search-civil-tasksSearch civil tasksReadMedium

Search available civil-service actions by purpose so the correct government workflow can be selected before authentication or submission.

Inputs
  • querystringRequiredPurpose or service name the user wants to complete.Example resident certificate
Outputs
servicesservice_nameportalrequired_authresult_type
Acceptance
  • Returns candidate government tasks that match the user's purpose.
  • Returns only civil-service tasks that Gov24 actually offers.
  • Does not imply submission is possible before the relevant portal and prerequisites are identified.

Must work without account auth.

check-required-docs-authCheck required documents and authentication methodReadMedium

Inspect a selected task to determine the identity verification method, attached documents, and any prerequisites needed before proceeding.

Inputs
  • task_idstringRequiredSelected civil-service task identifier.Example gov24-resident-certificate
Outputs
required_documentsauthentication_methodeligibilitysubmission_windowfee
Acceptance
  • Lists the documents or identity checks needed for the selected task.
  • Separates portal-specific authentication from general eligibility requirements.
  • Returns missing prerequisites instead of assuming the user can proceed immediately.

Must work without account auth.

prepare-certificatePrepare certificate issuance workflowWriteHard

Build a draft for certificate issuance using the required personal and case details, then return a reviewable submission package.

Inputs
  • task_idstringRequiredGovernment task identifier.Example gov24-family-relation-certificate
  • profileobjectRequiredMinimal user or case information needed to populate the draft without leaking unnecessary personal data.Example {"name":"Kim Min-su","residentIdLast4":"1234"}
  • attachmentsarrayOptionalOptional supporting documents or attachment references required by the workflow.Example ["supporting_document.pdf"]
Outputs
draft_idrequired_fieldssubmission_summarydeadlineestimated_fee
Acceptance
  • Builds a draft only when the required task fields are available.
  • Returns a review summary that exposes the final submission shape before any request is sent.
  • Avoids echoing full sensitive identifiers in outputs or notes.

Auth required for this API.

submit-approved-requestSubmit approved requestWriteHard

Send a prepared government request after explicit user approval and return the resulting application identifier.

Inputs
  • draft_idstringRequiredDraft identifier created by the preparation step.Example draft_4c2b1
  • user_approvedbooleanRequiredExplicit confirmation that the user reviewed the draft and agreed to submit it.Example true
  • payment_methodstringOptionalOptional payment token or account reference if a fee must be charged.Example bank_transfer_token
Outputs
application_idsubmitted_atreceipt_numberpayment_statusstatus
Acceptance
  • Refuses to submit if the user approval flag is absent or false.
  • Returns an application or receipt identifier after successful submission.
  • Surfaces payment or portal validation failures rather than pretending the request was accepted.

Auth required for this API.

get-application-statusGet application statusReadMedium

Check the progress of a certificate or application request and return the current status, timestamps, and next action if one exists.

Inputs
  • application_idstringRequiredApplication or receipt number to track.Example APP-20260715-0091
Outputs
statusapplication_idsubmitted_atprocessed_atnext_step
Acceptance
  • Returns a concrete status for the supplied application identifier.
  • Includes timestamps or next-step guidance when the portal exposes them.
  • Does not fabricate completion if the request is still pending or under review.

Auth required for this API.

download-issued-documentsDownload issued documentsReadMedium

Retrieve issued certificates, receipts, or payment confirmations after the corresponding request has completed successfully.

Inputs
  • document_idstringRequiredIssued document, receipt, or confirmation identifier.Example RCPT-20260715-7781
  • formatstringOptionalOptional file format preference for the download.Example pdf
Outputs
file_namedownload_urlissued_atdocument_typedocument_id
Acceptance
  • Returns only documents that were actually issued for the authenticated user.
  • Provides a downloadable artifact or direct file reference when the portal supports it.
  • Rejects access when the document has not yet been issued or the identifier is invalid.

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.