e-Tax
OpenJapanese tax workflows for filings, certificates, and status tracking on e-Tax.
- Reward
- ₩500,000
- Tier
- Platinum
- Auth
- Browser
- APIs
- 6 APIs
- Working now
- none
- Posted
- 2026-07-07
- Kind
- New service
- Open
- Claimed
- In review
- Finalizing
- Syncing
- Merged
- Paid
Scope
Build a high-trust Japanese tax workflow provider for e-Tax. It must handle My Number authentication boundaries, prepare tax filings, show all submission details, require explicit approval, and retrieve status or receipts without exposing sensitive data in logs.
Expected APIs
6search-proceduresSearch government or tax proceduresReadHard
Search available tax procedures on e-Tax by keyword and category. This targets the authenticated browser surface, not a public REST API.
keywordstringOptionalProcedure keywordExamplefinal tax returncategorystringOptionalProcedure categoryExampletaxfiscal_yearstringOptionalTarget fiscal yearExample2025
- Returns procedures matching the keyword or category from the authenticated portal.
- Each procedure indicates whether a My Number card is required and if online submission is available.
- Does not claim a public API; results come from the logged-in browser session.
Auth required for this API.
check-prerequisitesCheck identity and document prerequisitesReadHard
Check the identity, My Number card, e-certificate, and document prerequisites required to start a selected procedure.
procedure_idstringRequiredProcedure identifierExampleproc_final_return
- Returns the required documents and authentication level for the procedure.
- Flags whether card-based authentication or an e-certificate is mandatory.
- Reports prerequisite_status so the user knows if they can proceed.
Auth required for this API.
prepare-filingPrepare benefit, certificate, or tax filingWriteHard
Assemble a benefit application, certificate request, or tax filing draft with the collected inputs for review. This prepares but does not submit the request.
procedure_idstringRequiredProcedure identifierExampleproc_final_returnform_dataobjectRequiredCollected form field valuesExample{"income":5200000}attachmentsarrayOptionalReferences to prepared attachmentsExample["withholding_slip"]
- Produces a filing draft with any validation_warnings and requires_confirmation true.
- Does not submit to the agency; only a reviewable draft is returned.
- Missing mandatory formData fields are surfaced as validation warnings.
Auth required for this API.
submit-requestSubmit an approved requestWriteHard
Submit a prepared draft to the government or tax authority, executed only after explicit user confirmation through the authenticated session.
draft_idstringRequiredPrepared draft idExampledrft_final_2025confirmationbooleanRequiredExplicit user confirmation flagExampletrue
- Submits only when confirmation is true and a valid draftId exists.
- Returns a submission_id and receipt_number issued by the authority.
- A draft failing prerequisite checks is not submitted.
Auth required for this API.
get-statusGet application, filing, or payment statusReadHard
Retrieve the current status of a submitted application, tax filing, or payment from the portal.
submission_idstringRequiredSubmission identifierExamplesub_88213
- Returns the current status and last update time for the submission_id.
- Includes payment_status when the procedure involves a payment.
- An unknown submission_id returns an explicit not-found result.
Auth required for this API.
download-documentsDownload receipts, notices, or issued documentsReadHard
Download issued receipts, notices, or certificates produced by a completed procedure through the authenticated session.
submission_idstringRequiredSubmission identifierExamplesub_88213document_typestringOptionalDocument type to downloadExamplereceipt
- Returns downloadable document references only for the authenticated user's completed procedures.
- Distinguishes receipts, notices, and issued certificates via document_type.
- Documents not yet issued return a pending state rather than a broken link.
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.