Idempotent status checks
SHIPPEDBefore every upload we call TimeCheckStatus to see if the month is empty, individually filed, bulk-filed, or already locked. No accidental overwrites of a month that's been submitted.
The Goa Department of Tourism requires 3 months of clean staging submissions before issuing production credentials for the TIME app. LivAround files every monthly Form XI for you, drafts the email that unlocks production, and runs every month after on autopilot. You set it up once.
The Department of Tourism requires every hotel to clear a 3-month testing window on the TIME app's staging environment before issuing production credentials. LivAround manages the journey from day one to production cutover.
Host registers at goaonline.gov.in & receives HOTXXXXXXX
First Form XI submission to DoT staging endpoint. We pre-populate, you confirm.
~30 min reviewSame flow. Submission history builds in your dashboard for the audit trail.
~15 min reviewFinal qualifying month. We auto-draft the production access email to DoT.
3/3 unlocks emailDoT issues your per-hotel AuthKey. Paste it once. Every future month flows to production.
~1 week responseFour steps from "I just got my hotel registered" to "every month files itself." Today, you review and confirm each month. Daily auto-upload and 1st-of-month auto-submit are next on the roadmap.
One-time signup at goaonline.gov.in — upload authority letter, complete OTP verification, wait for SMS approval. We'll guide you with a 2-min walkthrough.
Paste your HotelID into the TIME settings card. Module activates in staging mode. Encrypted at rest, scoped per property.
End of month, we pre-populate Form XI from your bookings. Review, edit if needed, click submit. We POST to DoT's staging API and log the response.
After 3 clean staging months, we draft the spec-formatted email to tourism@goaelectronics.co.in. DoT replies with your AuthKey. Paste, flip the toggle, you're live.
The DoT requires 14 fields per checkout — age buckets, gender split, country, state, room nights, nightly rate, purpose of visit. LivAround pulls the data we already have, derives what we can, and asks guests for the rest at pre-arrival.
No spreadsheets. No copy-pasting between your PMS and goaonline.gov.in. Country and state enums match the DoT spec exactly — typos preserved — so your uploads never get rejected for a misspelled "United States."
The TIME API is unforgiving — wrong date format, unrecognized country, unknown month state, and the upload silently fails or freezes the wrong period. We built every guardrail.
Before every upload we call TimeCheckStatus to see if the month is empty, individually filed, bulk-filed, or already locked. No accidental overwrites of a month that's been submitted.
Every payload validated against the DoT schema before we POST — country in the official 248-entry enum, state required only for India, age buckets that sum to total guests. Catches errors before they become rejections.
HotelID and HotelAuthKey stored encrypted at rest, scoped per property. Production keys (post 3-month testing) replace staging without code changes — paste and toggle.
DoT requires dates as 12-Feb-2025. We use a fixed UTC formatter — never the platform locale, which would silently break in production. Every date in every payload, every time.
Today, you submit each month from your dashboard. Next: a nightly job (mirroring our calendar sync) pushes each day's checkouts to DoT in Individual mode — the format DoT recommends for daily uploads.
Coming with the scheduler: a 3-day review window opens the 1st of every month, then auto-calls TimeSubmitData on the 4th. A red flag in your dashboard within hours of any failure — never silent.
No add-ons. No per-submission fees. TIME compliance ships with every Goa property — including hands-on guidance through your 3-month staging window and the production unlock email.
It's a Department of Tourism rule, not ours. The TIME API spec requires every hotel to operate against the staging environment for at least 3 months of clean submissions before they'll issue production credentials. The intent is to verify your integration works correctly before live data flows.
What that means in practice: for those 3 months, your data files against staging (it doesn't reach the production tourism dataset). After the 3rd successful month, we email tourism@goaelectronics.co.in with the spec-formatted subject line on your behalf. DoT then issues your per-hotel HotelAuthKey for production.
Shipped today: the API integration (status check, upload, submit), DoT-spec validation (country/state enums, dd-Mon-yyyy date format, age bucket math), per-property encrypted auth keys, and a dashboard where you review and submit each month.
Next on the roadmap: a nightly job that pushes each day's checkouts to DoT in Individual mode, and a 1st-of-month auto-submit with a 3-day review window. Both follow the same pattern as our existing iCal calendar sync — battle-tested architecture.
Yes — registration is a one-time manual step. You'll need to upload an authority letter, complete OTP verification, and wait for DoT approval (an SMS will confirm). Once approved, paste your HotelID into LivAround and we handle every monthly filing from then on.
We're shipping a guided 2-minute walkthrough to make registration painless — including the authority letter template and a checklist of documents DoT asks for.
The TIME spec is ambiguous on what counts as a "successful" month if you skip one. Conservative interpretation: skipped or failed months may not count toward your 3-month total, and DoT may push back when we email for production access.
Our recommendation — and what the upcoming scheduler enforces — is consecutive months. If you forget, the auto-submit job (1st of next month) catches it. If a submission fails for a technical reason, you'll see a red flag in your dashboard within hours, not weeks.
purposeOfVisit to Leisure — which is honest for the channel and accepted by DoT. For direct or non-Airbnb bookings, our pre-arrival messaging asks the guest directly. You can always override before the month is submitted.TimeSubmitData for a month, that month freezes and cannot be modified — that's a DoT-side rule, not ours.We commit to best-effort, retry-on-failure delivery and full audit logs of every API call. Final compliance responsibility remains with the host — that's standard for any compliance automation tool.
In practice: you'll see a flag in your dashboard within hours of any failure, we don't go silent, and every API call is logged with DoT's exact response so you have proof of timely submission. Full terms in our terms of service.
The sooner your first staging submission lands, the sooner you're production-cleared. Three months passes faster than you'd think — especially when LivAround handles every filing for you.