Aq Qoyunlu–Mamluk War (1470–1474)
1470–1474 war

The Aq Qoyunlu–Mamluk War was a conflict fought between the Aq Qoyunlu confederation and the Mamluk Sultanate from 1470 to 1474. The war was sparked by Aq Qoyunlu raids into Mamluk territories in Syria and Upper Mesopotamia and culminated in a series of battles, including the failed sieges of Bira and Bilecik. The war ended with a decisive Mamluk victory and marked the beginning of Aq Qoyunlu's decline.
Background
The Aq Qoyunlu Turkmen confederation emerged as a major power in Southwest Asian politics during the second half of the 15th century, following the decline of the Ilkhanate.
In 1429, Qara Yuluk Uthman Beg, founder of the Aq Qoyunlu dynasty, launched an attack on the Dulkadirids—then vassals of the Mamluk Sultanate—and appointed his son Ali Beg as governor over the conquered region. In response, the Mamluks raided Urfa, capturing both Ali Beg and another Aq Qoyunlu commander, Abul Bey. The Mamluks then proceeded to besiege the Aq Qoyunlu capital. Although the siege ended in a stalemate, Uthman Beg ultimately submitted to Mamluk authority and recognized their suzerainty.
During his first decade of rule, Uzun Hasan secured a series of victories against two of his main rivals: Jahan Shah of the Qara Qoyunlu federation and the Timurid ruler of Bukhara. In 1467, the Dulkadirid ruler Shah Suwar revolted against the Mamluks and maintained independence for three years.
This brief starts where responsible research should: with the source description of “Aq Qoyunlu–Mamluk War (1470–1474)” as 1470–1474 war. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as 1470–1474 war. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Aug 21, 2026. The linked authority identifier is Q134311925. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1470, 1474, 1429 and 1467.
Institutional narratives can privilege the records that survived while minimizing voices that were never formally collected. 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 “Aq Qoyunlu–Mamluk War (1470–1474)”, its source revision and the description used here.
- Expand the search: follow Aq Qoyunlu–Mamluk War (1470–1474) primary sources, Aq Qoyunlu–Mamluk War (1470–1474) archive and Qoyunlu 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 “Aq Qoyunlu–Mamluk War (1470–1474)”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Aq Qoyunlu–Mamluk War (1470–1474)” 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.