Salik, Parkin and nol Integration for Dubai Apps in 2026: APIs, VAT and Real Costs

Short answer: in 2026 you can integrate a Dubai app with the toll, parking and transit layer — but not the way most teams budget for it. Salik publishes its tariff as an open dataset on Dubai Pulse and settles fleet usage through corporate account statements, not a public per-crossing webhook; Parkin bills through its own app and payment rails; and nol is mid-rebuild, with RTA 72% through an AED 550 million migration to account-based ticketing that finishes by Q1 2027. The thing that actually broke production systems this year was simpler: on 1 June 2026 a 5% VAT landed on Salik tolls, Salik tag activation and Parkin parking, turning every hard-coded AED 4 and AED 6 constant in a fleet billing engine into a wrong number.

Key takeaways

• VAT changed the arithmetic on 1 June 2026. A peak crossing is now AED 6.30 and an off-peak crossing AED 4.20. Parking is taxed too, and cash at Parkin meters stopped the same day.
• Tolls are time-variable, not flat. Since 31 January 2025 Salik charges by time of day across 10 gates — peak, off-peak, a free window and a different Sunday rule. A single rate constant cannot model it.
• The volume is why this is worth engineering. Salik ran 383.8 million toll trips in H1 2026 across 2.9 million active accounts; Parkin processed 141 million parking transactions in 2025.
• nol is a moving target. Build against the account, not the card. Account-based ticketing with QR, wallets and bank cards arrives in early 2027.
• Most Dubai fleet apps get this wrong the same way. They scope a live toll API that is not publicly self-serve, then discover in UAT that the real integration is statement reconciliation plus a tariff engine.

Dubai's mobility layer is now a billing system

Tolls, parking and transit stopped being municipal line items and became high-frequency transaction streams that your software has to reconcile. Salik reported AED 1.41 billion of revenue and AED 704 million of net profit in H1 2026 on 383.8 million toll trips, with 2.9 million active registered accounts. Parkin cleared 141 million parking transactions in 2025 across roughly 229,000 paid spaces, and posted AED 384.2 million of revenue in Q1 2026, up 41% year on year.

Transit is the same story at higher frequency. Dubai residents completed 628 million RTA transactions digitally in 2025, and nol cards alone now run more than 1.5 million transactions a day. Against that, the UAE fleet management software market is valued at about USD 245 million and forecast to reach USD 613 million by 2032 at a 6.5% CAGR — growth that is being paid for by operators who want these three streams inside one dashboard instead of three portals and a spreadsheet.

If you run a rental fleet, a delivery operation, a valet business or a mobility app, every one of those transactions is either a cost you recharge or a cost you absorb. The difference between the two is code.

What changed on 1 June 2026, and what it broke

From 1 June 2026, 5% VAT applies to Salik toll tariffs, Salik tag activation fees, and Parkin on-street and off-street parking. The headline numbers moved:

Charge	Before 1 Jun 2026	From 1 Jun 2026	What your code must do
Salik peak crossing (06:00–10:00, 16:00–20:00)	AED 6.00	AED 6.30	Store net and VAT separately, never one gross constant
Salik off-peak crossing (10:00–16:00, 20:00–01:00)	AED 4.00	AED 4.20	Same, with a second tariff band
Salik late night (01:00–06:00, daily)	AED 0.00	AED 0.00	Zero-rate window must exist as a rule, not an exception
Sunday crossings (excl. holidays and events)	AED 4.00 all day	AED 4.20 all day	Day-of-week override that beats the peak rule
Salik tag activation	AED 100	AED 105	Fleet onboarding cost per vehicle, recoverable input tax
Parkin on-street and off-street	Tariff only	Tariff + 5% VAT	Cash at meters ended; digital payment is now mandatory

This is where the damage happened. Fleet systems built before 2025 typically stored a single toll rate. Systems built after January 2025 usually stored two. Almost none stored a tax-exclusive rate with an effective-from date, which is exactly what a 1 June rate change demands — because June invoices have to be split at the boundary, and April statements must keep reproducing the old figure forever. If you recharge tolls to customers or to employees, that arithmetic is now the difference between a clean VAT return and a restatement. The same effective-dating discipline your invoicing stack needs is covered in our UAE e-invoicing ERP integration guide.

The recoverable half is the good news: registered businesses can generally claim the VAT on Salik and parking as input tax where the vehicles are used for taxable business activity — provided your system actually carries the tax amount, the supplier TRN and the document reference through to the return. A gross-only number is an unrecoverable number.

What you can actually integrate with in 2026

Here is the honest availability map. Scope from this table, not from an assumption that everything has a REST endpoint.

Source	What is available	Integration method	Practical effort
Salik tariff data	Published tariff dataset on Dubai Pulse	Dubai Pulse OAuth client credentials, bearer token	Low — days
Salik crossings (fleet)	Account statements and usage exports on the corporate account	Scheduled statement ingestion, parse and normalise	Medium — the real work
Parkin usage	Session and payment records from your own paid-parking workflow	Capture at point of payment, reconcile to statements	Medium
nol	Card-based today; account-based ticketing from early 2027	Design against an account abstraction now, not a card number	Plan now, build 2027
RTA open data	Bus routes, bus stops, metro ridership and more on Dubai Pulse	API key and secret per dataset grant, OAuth token	Low
Government identity	UAE Pass for driver and customer onboarding	OIDC integration	Low — see our UAE Pass guide

Two details catch teams out on Dubai Pulse specifically. First, credentials are issued as a separate API key and API secret when a dataset is granted — they are not a login. Second, the OAuth token is short-lived, on the order of 30 minutes, so any integration that caches a token for a day will start failing silently at exactly the wrong hour. Refresh on 401, and refresh proactively.

On Salik itself: a tag is bound to one vehicle and cannot be moved between vehicles, corporate tags run at AED 100 each before VAT, and rental cars ship with pre-activated tags. Your vehicle master data therefore needs a tag-to-vehicle-to-contract chain with dates, or you will bill the wrong renter for a crossing that happened during a handover.

The architecture that actually survives

Every working implementation we have shipped looks roughly the same, because the constraints are the same for everyone.

1. A tariff engine, not a rate column

Model tariffs as rules with a valid-from and valid-to date: gate, day type, time window, net amount, tax rate. Peak, off-peak, the free 01:00–06:00 window, the flat Sunday rate and the public-holiday and event exceptions are all just rows. When RTA changes a band — and it has more than once since January 2025 — you insert a row instead of shipping a release.

2. Reconciliation as a first-class pipeline

Ingest the statement, match each crossing to a vehicle, then to a trip or rental contract by timestamp, then to a customer. Keep the unmatched queue visible; at 383.8 million trips of national volume, even a fleet of 200 vehicles generates enough edge cases that a silent fallback will quietly eat margin.

3. Recharge rules a finance team can audit

Absorb, recharge at cost, or recharge with an admin fee — whichever you choose, store the net, the VAT and the rule applied on each line. That is what makes your rental or booking platform defensible when a customer disputes an AED 6.30 charge from a Tuesday morning.

4. An account abstraction for nol

RTA is 72% through the AED 550 million shift from card-based to account-based ticketing, completing by the end of Q1 2027, after which riders pay by QR, digital wallet or bank card and next-generation nol cards work like bank cards at retail. If your data model keys on a card serial today, you will rewrite it in 2027. Key on an account with cards attached, and you will not.

What it costs to build in Dubai, in AED

Real ranges for the mobility integration layer, separate from the fleet or booking product it plugs into.

Scope	AED range	Typical timeline
Tariff engine and VAT-correct toll and parking costing	18,000 – 35,000	2 – 3 weeks
Statement ingestion, matching and exceptions queue	30,000 – 65,000	3 – 5 weeks
Dubai Pulse open-data integration (tariff, transport datasets)	9,000 – 20,000	1 – 2 weeks
Recharge, invoicing and VAT reporting hooks into your ERP	25,000 – 60,000	2 – 4 weeks
Full fleet mobility-cost module inside an existing platform	85,000 – 180,000	8 – 12 weeks
Ongoing maintenance and tariff or regulation updates	2,500 – 7,000 / month	—

Add 5% VAT to those figures, and check the supplier TRN appears on the invoice so you can reclaim it. Now weigh it against the cost of inaction: the weighted average hourly public parking tariff in Dubai rose 51% year on year to AED 3.02 in Q1 2026, and a single peak crossing went from AED 6.00 to AED 6.30. A fleet of 150 vehicles averaging six peak crossings a working day carries roughly AED 1.4 million a year in tolls alone, before parking. Recovering even the slice that should have been recharged to customers pays for the entire build inside a quarter — and mis-stated VAT on that base is not a rounding error.

How Aquarius builds it

We start with the reconciliation question, not the dashboard: what source of truth exists, how often it lands, and what has to match to what. That answer dictates the schema, and the schema is the part that is expensive to change later. We build the tariff engine effective-dated from day one, so the next RTA announcement is a configuration change and not an incident.

Beyond that: net and VAT stored separately on every line, an exceptions queue a human can clear, an export your accountant can drop straight into a VAT return, Arabic-first RTL screens where drivers use them, and UAE-resident hosting when data residency is in scope. You get the repository, the cloud account and the domain — nothing about your platform stays hostage with us. See our pricing and what each service includes, or the broader logistics and fleet tracking build guide.

If your fleet is small enough that a monthly spreadsheet still works, we will tell you that and scope the smaller thing. Send us your brief and we will come back with a component list and an AED number.

FAQ

Is there a public Salik API for real-time crossings?

Not as a self-serve public API. Dubai Pulse publishes RTA's Salik tariff as an open API dataset, and fleet operators get usage through the Salik corporate account and its statements. Practical integrations reconcile from statements against your own trip data rather than listening to a live per-crossing feed. For large fleets, ask Salik about a consolidated monthly tax invoice arrangement before you design the ingestion.

How much is a Salik crossing in 2026?

Since 1 June 2026 a peak crossing costs AED 6.30 including 5% VAT and an off-peak crossing AED 4.20. Peak runs 06:00–10:00 and 16:00–20:00; there is no charge between 01:00 and 06:00 any day; and Sundays are charged at the off-peak rate all day, excluding public holidays and special events.

Can my business reclaim the VAT on Salik and parking?

Generally yes, as input tax, where the vehicles are used for taxable business activities and you hold valid documentation. That is a software requirement as much as a tax one: your system has to store the tax amount, the supplier TRN and the reference on each line from 1 June 2026 onward, and keep pre-June records at the old treatment.

Should I build against nol now or wait?

Build the abstraction now, integrate later. RTA is 72% through an AED 550 million migration to account-based ticketing due to complete by the end of Q1 2027, bringing QR, digital wallet and bank card payment plus next-generation nol cards usable like bank cards. Anything you key on a card serial today gets rewritten then.

How do I get Dubai Pulse API access?

Request the dataset on Dubai Pulse; an API key and API secret are issued on first grant, and you exchange them at the OAuth client-credentials endpoint for a bearer token with a short life — around 30 minutes — that you refresh on expiry. Treat the secret like any other production credential and never ship it in a mobile binary.

Does this apply outside Dubai?

Partly. Salik and Parkin are Dubai systems; Abu Dhabi runs Darb with its own tariff structure and rules. If you operate across emirates, the tariff engine needs an operator dimension from the start, which costs almost nothing in week one and is a migration later.