Amara Sullia Rebellion
Armed uprising against British Rule in British India

The Amara Sullia Rebellion (also called Kalyanappana Katakayi or Amara Sulya Raitha) was an armed uprising against the British government organized by the people of Arebhashe, Kodava people, and Tulunadu that took place in 1837, twenty years before the Sepoy Mutiny of 1857.
The Amara Sullia Rebellion was basically a farmers’ rebellion.
The reason for the rebellion in Sullia was that the British dethroned the ruler of Kodagu, Chikkaveerrarajendra of Haleri dynasty in 1834 and later he was transferred to Bellore.
History
In 1799, South Kanara came under British rule. But until Chikkaviraraja (1820–1844), the last of the Haleri chiefs, was overthrown, Coorg had a tenuous sense of independence. After Coorg was annexed, the Amarsullian magane and Puttur, which the British had given to the Raja of Coorg in 1804 for their convenience, were moved to the province of Kanara. It caused the inhabitants of these moved maganes to endure great suffering.They initially observed a shift in the way taxes were paid to the government. The revenue was given in kind during the reign of the Rajas of Coorg.
Reasons
There was a tradition of paying revenue to the monarch in the form of products before the Sulya Puttur of Dakshina Kannada became a province of Canara. Despite this, the British issued instructions requiring the residents of Kodagu and Dakshina Kannada to pay taxes in cash.
This brief starts where responsible research should: with the source description of “Amara Sullia Rebellion” as armed uprising against British Rule in British India. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as armed uprising against British Rule in British India. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Jul 30, 2026. The linked authority identifier is Q108142412. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1837, 1857, 1834 and 1799.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Amara Sullia Rebellion”, its source revision and the description used here.
- Expand the search: follow Amara Sullia Rebellion primary sources, Amara Sullia Rebellion archive and Amara research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Amara Sullia Rebellion”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Amara Sullia Rebellion” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.