WordPress at a glance

add_rewrite_endpoint() WP 1.0

Add an endpoint, like /trackback/.

Adding an endpoint creates extra rewrite rules for each of the matching places specified by the provided bitmask. For example:

add_rewrite_endpoint( 'json', EP_PERMALINK | EP_PAGES );

will add a new rewrite rule ending with "json(/(.*))?/?$" for every permastruct that describes a permalink (post) or page. This is rewritten to "json=$match" where $match is the part of the URL matched by the endpoint regex (e.g. "foo" in "[permalink]/json/foo/").

A new query var with the same name as the endpoint will also be created.

When specifying $places ensure that you are using the EP_* constants (or a combination of them using the bitwise OR operator) as their values are not guaranteed to remain static (especially EP_ALL).

Be sure to flush the rewrite rules - see flush_rewrite_rules() - when your plugin gets activated and deactivated.

No Hooks.


Null. Nothing.


add_rewrite_endpoint( $name, $places, $query_var );
$name(string) (required)
Name of the endpoint.
$places(int) (required)
Endpoint mask describing the places the endpoint should be added.
Name of the corresponding query variable. Pass false to skip registering a query_var for this endpoint.
Default: value of $name


  • Global. WP_Rewrite. $wp_rewrite WordPress rewrite component.


Since 2.1.0 Introduced.
Since 4.3.0 Added support for skipping query var registration by passing false to $query_var.

Code of add_rewrite_endpoint() WP 5.6

function add_rewrite_endpoint( $name, $places, $query_var = true ) {
	global $wp_rewrite;
	$wp_rewrite->add_endpoint( $name, $places, $query_var );

From tag: Rewrite (clean friendly URL)

No comments
    Log In