Skip to content

Add Threads as an oEmbed provider#11252

Open
pestevez wants to merge 10 commits intoWordPress:trunkfrom
pestevez:add/threads-oembed-provider
Open

Add Threads as an oEmbed provider#11252
pestevez wants to merge 10 commits intoWordPress:trunkfrom
pestevez:add/threads-oembed-provider

Conversation

@pestevez
Copy link

Trac ticket: https://core.trac.wordpress.org/ticket/64858

Description

Adds Threads as a built-in oEmbed provider. Threads recently dropped the access token requirement, making tokenless oEmbed possible via graph.threads.com/oembed.

Changes

  • Registered two provider patterns in class-wp-oembed.php covering both URL formats
  • Added documentation table entries
  • Added PHPUnit test file with 14 test cases

Supported URL formats

  • https://www.threads.com/@{username}/post/{shortcode}
  • https://www.threads.com/t/{shortcode}

Both threads.com and threads.net domains supported, with and without www., over http and https.

Testing

PHPUnit tests included: 10 positive match tests + 4 negative tests.

Manual: paste a Threads post URL in the classic editor or via the REST API oEmbed proxy and verify the embed resolves.

Use of AI Tools

Created using Claude Code (Opus 4.6)

@github-actions
Copy link

Hi @pestevez! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions
Copy link

github-actions bot commented Mar 14, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props pmestevez, westonruter.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

pestevez and others added 7 commits March 14, 2026 14:49
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Co-authored-by: Weston Ruter <westonruter@gmail.com>
Comment on lines +21 to +26
/**
* @dataProvider data_threads_provider_urls
*
* @param string $url The URL to test.
* @param string $expected The expected oEmbed provider URL.
*/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/**
* @dataProvider data_threads_provider_urls
*
* @param string $url The URL to test.
* @param string $expected The expected oEmbed provider URL.
*/
/**
* @ticket 64858
*
* @dataProvider data_threads_provider_urls
*
* @param string $url The URL to test.
* @param string $expected The expected oEmbed provider URL.
*/

Add @ticket annotation to all new tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants