Skip to content
/bounty
Sign in
All bounties

RTA

Open
rta.ae

Dubai transport self-service for fines, parking, vehicle status, and account management on RTA.

Reward
₩300,000
Tier
Gold
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-driven RTA provider for Dubai drivers. It should cover account and vehicle summaries, fine and parking lookups, permit requests, payment preparation, explicit approval before confirmation, and receipt or case-status retrieval.

Expected APIs

6
get-account-vehicle-summaryGet account and vehicle summaryReadMedium

Retrieve the user's RTA account overview together with linked vehicles, balances, and permit status. This is the main read path for transport account management.

Inputs
  • account_numberstringRequiredRTA account identifier.Example RTA-123456
  • vehicle_platestringOptionalVehicle plate to narrow the lookup when needed.Example A12345
Outputs
account_numbervehiclesbalancetag_statusstatus
Acceptance
  • Returns the linked vehicles and current account balance for the requested user.
  • Includes linked-vehicle registration and permit status for the account.
  • Does not mix vehicles from unrelated transport accounts.

Auth required for this API.

search-fines-trips-permits-disputesSearch fines, trips, permits, and disputesReadMedium

Look up fines, parking sessions, toll trips, permits, and dispute cases tied to the account or vehicle. This gives the user the context needed before payment or follow-up.

Inputs
  • account_numberstringRequiredAccount to search against.Example RTA-123456
  • plate_numberstringOptionalVehicle plate for a narrower search.Example A12345
  • case_typestringOptionalType of record to search for.Example fines
Outputs
finesparking_sessionstoll_tripspermitsdisputes
Acceptance
  • Returns the matching fine, trip, permit, or dispute records for the chosen account or vehicle.
  • Shows enough metadata to distinguish unpaid items from informational history.
  • Keeps parking sessions separate from toll-trip history.

Auth required for this API.

prepare-recharge-or-paymentPrepare recharge or paymentWriteHard

Assemble a draft for fine payment, parking-related payment, or permit request without finalizing it. The draft should capture the plate, amount, fees, and payment method details.

Inputs
  • account_numberstringRequiredAccount to fund or charge.Example RTA-123456
  • request_typestringRequiredType of transport action to prepare.Example recharge
  • amountnumberRequiredAmount to recharge or pay.Example 100
  • plate_numberstringOptionalVehicle plate associated with the request.Example A12345
Outputs
draft_requestamountfeesplate_numbervalidation_status
Acceptance
  • Creates a draft without charging the account or finalizing the request.
  • Carries the amount, fees, and plate details into review.
  • Rejects incomplete drafts when required account or amount fields are missing.

Auth required for this API.

review-transport-payment-detailsReview transport payment detailsReadHard

Show the plate, tag, amount, fees, payment method, and terms before final confirmation. This is the last checkpoint before a transport payment or request is submitted.

Inputs
  • draft_requestobjectRequiredDraft returned by the preparation step.Example {...}
Outputs
plate_numbertag_numberamountfeespayment_methodterms
Acceptance
  • Shows the exact plate, tag, amount, and fee breakdown before submission.
  • Displays the payment method and terms that will apply to the transaction.
  • Makes it possible to catch bad plate or tag data before approval.

Auth required for this API.

confirm-transport-paymentConfirm transport paymentWriteHard

Finalize the prepared recharge, fine payment, parking payment, or permit request only after the user explicitly approves the draft.

Inputs
  • draft_requestobjectRequiredConfirmed transport draft ready to submit.Example {...}
  • approvalbooleanRequiredExplicit user approval to complete the payment or request.Example true
Outputs
transaction_idstatusreceipt_numberpayment_statuscase_id
Acceptance
  • Does not complete the action without explicit approval.
  • Returns a transaction, receipt, or case reference after success.
  • Reports the resulting payment state and any linked case identifier.

Auth required for this API.

get-receipts-and-balance-updatesGet receipts and balance updatesReadMedium

Fetch the latest receipt, case status, service history, and balance updates for the account. Use this to confirm what changed after a payment or follow-up action.

Inputs
  • account_numberstringRequiredAccount number to query.Example RTA-123456
Outputs
receiptscase_statusvehicle_servicesbalanceupdated_at
Acceptance
  • Returns receipt references and the latest case or service status for the account.
  • Includes balance updates after recharge or payment when available.
  • Keeps successful actions distinct from pending follow-up work.

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.