Deccan wars
wars between the Maratha Empire and the Mughal Empire

The Deccan wars, also known as Mughal–Maratha wars, were a series of military conflicts between the Mughals and the Marathas after the death of Maratha Chhatrapati Shivaji in 1680 until the death of Mughal Emperor Aurangzeb in 1707. Shivaji was a central figure in what has been called "the Maratha insurgency" against the Mughal state. Both he and his son, Sambhaji (or Shambuji, typically), alternated between rebellion against the Mughal state and service to the Mughal sovereign in an official capacity. It was common practice in late 17th-century India for members of a ruling family of a small principality to both collaborate with and rebel against the Mughals.
Upon Shivaji's death in 1680, he was immediately succeeded by Rajaram, his second-born son by his second wife. The succession was contested by Sambhaji, Shivaji's first-born son by his first wife, and quickly settled to his benefit by the murders of Rajaram's mother and the loyal courtiers favouring Rajaram's succession, and by Rajaram's imprisonment for the following eight years. Although Sambhaji's rule was riven by factions, he conducted several military campaigns in southern India and Goa.
In 1681, Sambhaji was contacted by Muhammad Akbar, son of Mughal Emperor Aurangzeb, who was keen to partner with the Marathas in order to assert his political power against his ageing father's continuing dominance. The prospects of an alliance incited Aurangzeb to move his household, court and army to the Deccan. Akbar spent several years under the protection of Sambhaji but eventually went into exile to Persia in 1686.
“Deccan wars” enters the record as wars between the Maratha Empire and the Mughal Empire. Crown Archives preserves that source wording while asking what Deccan, wars and between can confirm, complicate or overturn.
Why this record matters
“Deccan wars” is worth following because a concise public description often conceals a longer documentary argument. Here, Deccan, wars and between provides the most credible route into that argument.
Chronology, provenance and viewpoint should be read together before a broad social or political interpretation is accepted. The source revision retrieved here is dated Aug 22, 2026. The linked authority identifier is Q139845. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1680, 1707, 1681 and 1686.
Official terminology may obscure informal participation, dissent or communities documented only indirectly. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Deccan wars”, its source revision and the description used here.
- Expand the search: follow Deccan wars primary sources, Deccan wars archive and Deccan 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 “Deccan wars”?
- Which voices are present, absent or mediated by the institution?
- What chronology connects this entry to wider political or social change?
Search terms from this dossier
This entry incorporates text from “Deccan wars” 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.