{ "$schema": "https://govschema.org/spec/v0.3/govschema.schema.json", "govschemaVersion": "0.3.0", "id": "ke/immigration/eta-visa-application", "version": "1.0.0", "title": "Kenya Electronic Travel Authorisation (eTA) Application", "description": "The Directorate of Immigration Services' (Ministry of Interior and National Administration, State Department for Immigration and Citizen Services) Electronic Travel Authorisation (eTA), required of all foreign visitors except citizens of East African Community member states before travelling to the Republic of Kenya. Applied for live and unauthenticated at etakenya.go.ke — no account creation or login is required at any point walked in producing this schema. This schema models the individual (non-group), tourist/visitor pathway: the pre-wizard application setup (traveller category, country of residence, individual-vs-group application type), the Passport Information step (a passport bio-data-page upload that is OCR-processed live into structured fields the applicant then confirms), the Selfie or Photo step (a live-verified biometric face-match check against the passport photo, with an explicit override when the match fails), the Contact Information step (phone, email, address, occupation, and an emergency contact), the Trip Information step (travel reason), and the Arrival Details sub-step of Travel Information (arrival date and mode of arrival). It does not model the remainder of the Travel Information step (e.g. departure/accommodation details, not reached this session), nor the Customs Declaration, Required Documents, or Confirm and Proceed steps that follow in the live wizard's own step navigation — these are disclosed as an accepted scope boundary rather than silently omitted; no eTA fee was paid and no application was actually submitted in producing this schema. Filing this application is a traveller action performed directly with the Directorate of Immigration Services through etakenya.go.ke; this schema does not file the application itself, and the live source is always authoritative. GovSchema is independent and is not affiliated with, endorsed by, or operated by the Republic of Kenya or its Directorate of Immigration Services.", "status": "draft", "jurisdiction": { "country": "KE", "level": "national" }, "authority": { "name": "Directorate of Immigration Services (Ministry of Interior and National Administration, State Department for Immigration and Citizen Services)", "abbreviation": "DIS", "url": "https://www.etakenya.go.ke" }, "process": { "type": "application", "language": "en" }, "source": { "url": "https://www.etakenya.go.ke/form/apply/start", "retrievedAt": "2026-07-16", "documentRef": "The live etaKenya Electronic Travel Authorisation wizard, individual/tourist pathway, from application setup through the Arrival Details sub-step of Travel Information." }, "verification": { "method": "manual-source-review-v1", "lastVerifiedAt": "2026-07-16", "verifiedBy": "GovSchema Engineering (Standards Engineer)", "nextReviewBy": "2027-01-16", "notes": "GOV-3294 (\"GovSchema Standard Research\", follow-up to GOV-3288's scouting pass). Opens Kenya's Visa vertical (4/6; Kenya's Passport and DMV verticals were confirmed dead ends this same research cycle — both are eCitizen-SSO-gated with no unauthenticated field-level content). Walked live with Playwright + Chromium: home page -> \"Apply Now\" -> \"Tourists & Visitors\" (vs. Diplomats) -> \"How to Apply\" info page -> \"Declaration of Consent\" (a required terms checkbox) -> \"Country of Residence\" (a full-country picker, assigning a `draft_id` session identifier) -> \"Select Type\" (Individual vs. Group application) -> the numbered wizard (Passport information / Selfie or Photo / Contact Information / Trip Information / Travel Information / Customs Declaration / Required Documents / Confirm and Proceed). Two genuine biometric/document gates were defeated live rather than worked around: (1) the Passport Information step runs real OCR against the uploaded document — a synthetic solid-colour JPEG was rejected (\"Document processing unsuccessful... not clear enough\"), so a real, public-domain specimen passport bio-data-page image (Wikimedia Commons, `Bio_data_page_of_German_Passport.png`) was substituted, which the live OCR correctly read into six structured fields (full name, date of birth, nationality, issuer, document number, and validity/expiry date), each independently confirmed against the specimen's own printed values; (2) the Selfie step runs live facial-recognition matching between the selfie and the passport photo — a real but mismatched public-domain portrait photo (Wikimedia Commons, `Face_portrait_(Unsplash).jpg`) correctly triggered a \"Photo Mismatch\" warning, which the live UI allows overriding via an explicit \"Use this photo\" button (a soft warning, not a hard block) — used here to continue only for schema-fidelity purposes, not to claim a fraudulent identity match. This is the same class of finding as this registry's `tz/immigration/passport-application` and `rw/irembo/nida-diaspora-application` photo-upload gates, but genuinely deeper: full document OCR plus live face-matching, not just an image-quality check. The site is built on Phoenix LiveView (`data-phx-id` attributes, server-rendered DOM patches over a persistent websocket); its \"Continue\" buttons render with a genuine `disabled`/`opacity-50 cursor-not-allowed` state until all of a step's required fields validate — confirmed to require real keyboard input events (not just programmatic value-setting) to register, and used as live evidence that every field modelled `required: true` below is actually enforced. All enum value lists (`occupation`, 57 real options; `travelReason`, 12 real options; radio-button `arrivalMode`) were read directly from the live DOM's own `` element (e.g. \"Software and Applications Programmer\", \"Accountant, Economist, Finance Professional\", \"Student\", \"Retired\", \"Other (Please Specify)\"; the full list is reproduced in VERIFICATION.md).", "sourceRef": "Contact Information step, `#contact_info_occupation_id` (Validators.required, live-confirmed)", "validation": { "enum": [ "ACCOMMODATION_HOSPITALITY_CATERING_PROFESSIONAL", "ACCOUNTANT_ECONOMIST_FINANCE_PROFESSIONAL", "ACTOR", "ADVERTISING_MARKETING_PROFESSIONAL", "AGRICULTURAL_AGRONOMY_FISHERIES_FORESTRY_PROFESSIONAL", "AIR_OR_MARITIME_TRANSPORT_PROFESSIONAL", "ARCHAEOLOGIST", "ARCHITECTS_AND_LANDSCAPE_PROFESSIONAL", "AUTHOR", "CHIEF_EXECUTIVE_AND_MANAGING_DIRECTOR", "CONFERENCE_AND_EVENT_PROFESSIONAL", "CYBER_SECURITY_DEVELOPER", "DANCER_OR_CHOREOGRAPHER", "DRIVER", "ELECTRICIAN", "JUDICIAL_AND_OTHER_LEGAL_PROFESSIONAL", "LIBRARIAN", "LOBBYIST", "MANUFACTURER", "MEDICAL_PRACTITIONER", "METEOROLOGIST", "MILITARY", "MINISTER_OF_RELIGION", "MULTIMEDIA_SPECIALIST_AND_WEB_DEVELOPER", "MUSIC_PROFESSIONAL", "NOT_WORKING_BY_CHOICE", "PHOTOGRAPHER", "PLUMBER", "POLICE_OFFICER", "PROJECT_MANAGER", "PUBLIC_RELATIONS_PROFESSIONAL", "RESEARCH_AND_DEVELOPMENT", "RETIRED", "SALES_PROFESSIONAL", "SCHOOL_TEACHER_UNIVERSITY_LECTURER_AND_TUTOR", "SELF_EMPLOYED", "SOCIAL_WORKER", "SOFTWARE_AND_APPLICATIONS_PROGRAMMER", "SPORTS_COACH_INSTRUCTOR", "STUDENT", "SUPPLY_DISTRIBUTION_AND_PROCUREMENT_PROFESSIONAL", "TRANSLATOR", "VETERINARIAN", "OTHER", "ENGINEER", "FIRE_FIGHTER", "FLORIST", "EMPLOYEE_GOVERNMENT_ENTITIES", "GRAPHIC_AND_WEB_DESIGNER_ILLUSTRATOR", "HAIRDRESSER", "HISTORIAN", "HOUSEKEEPER", "HUMAN_RESOURCE_MANAGER", "ICT_PROFESSIONAL", "IMPORTERS_EXPORTERS_AND_WHOLESALER", "JEWELLER", "JOURNALIST_BLOGGER" ] } }, { "name": "emergencyContactName", "label": "Name", "type": "string", "required": true, "classification": "pii", "description": "The name of an emergency contact. The live page allows adding further emergency contacts via its own \"Add Another\" control; this schema models only the first (required) entry, since GovSchema's field model has no repeating/array type — see VERIFICATION.md.", "sourceRef": "Contact Information step, \"Emergency Contact\" section, `#full_name_0` (Validators.required, live-confirmed)", "validation": { "maxLength": 150 } }, { "name": "emergencyContactPhone", "label": "Phone Number", "type": "string", "required": true, "classification": "pii", "description": "The phone number of the (first) emergency contact.", "sourceRef": "Contact Information step, \"Emergency Contact\" section, `#hooked_phone-phone_number_0` (Validators.required, live-confirmed)", "validation": { "maxLength": 20 } }, { "name": "travelReason", "label": "Select travel reason", "type": "enum", "required": true, "description": "The traveller's reason for visiting Kenya, read directly from the live `