API talk:Embeddedin

Backlinks Watchlist

• Backlinks Watchlist, a tool with source for monitoring changes to the backlinks of a page. -- Green Cardamom (talk) 04:08, 15 May 2015 (UTC)

Question: What is the main difference between transcludein?

What is the main difference between embeddedin and API:Transcludedin? The first seems a legacy version of the second, but correct me if I'm wrong. --Valerio Bozzolan (talk) 16:57, 25 August 2018 (UTC)

I was curious about this too, so I looked into it. Here's what I found:

• list=embeddedin: Works the same as querying a page on Special:WhatLinksHere.
  • Functionality is provided by ApiQueryBacklinks.php.
  • The eititle parameter only accepts a single title.
  • The returned objects always have pageid, ns, and title properties.
• prop=transcludedin
  • Functionality is provided by ApiQueryBacklinksprop.php.
  • You can query multiple titles at once using the titles parameter.
  • The returned objects can be empty if you leave a **prop property empty (see this example, where prop=transcludedin&tiprop=).

Given this, I’d say prop=transcludedin is preferred over list=embeddedin in non-front-end environments, as it’s more resource-efficient and supports querying multiple pages at once. The same applies to list=backlinks vs prop=linkshere, and list=imageusage vs prop=fileusage, as these use the same underlying API modules. Dragoniez (talk) 10:31, 11 April 2025 (UTC)