# Wordpress custom API slug

**URL:** <https://community.make.com/t/wordpress-custom-api-slug/94716>\
**Category:** Questions\
**Tags:** wordpress\
**Created:** [October 23, 2025, 6:33pm UTC](https://community.make.com/t/wordpress-custom-api-slug/94716 "2025-10-23T18:33:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Riley](https://avatars.discourse-cdn.com/v4/letter/r/2acd7d/32.png) [@Riley](https://community.make.com/u/Riley)\
**Post date:** [October 23, 2025, 6:33pm UTC](https://community.make.com/t/wordpress-custom-api-slug/94716/1 "2025-10-23T18:33:57Z")

</div>

Hi all,

For security reasons, I changed my Wordpress API slug from /wp-json to something else. With the woocommerce node, you’re able to specify your site’s slug as the node asks for your url including the slug. However, the Wordpress node does not and appears to assume /wp-json.

Is there a way we can get Make to accept a new slug for the wordpress api?

---

<div class="post-metadata">

**Author:** ![ashleyharvey19](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@ashleyharvey19](https://community.make.com/u/ashleyharvey19)\
**Post date:** [October 28, 2025, 9:43pm UTC](https://community.make.com/t/wordpress-custom-api-slug/94716/3 "2025-10-28T21:43:07Z")

</div>

Creating a custom API slug in WordPress can be really useful for organizing endpoints and improving clarity in complex projects. I’ve done this by registering routes through register\_rest\_route() and defining unique namespaces for plugins. It keeps integrations cleaner, especially when multiple APIs coexist. Clear versioning within the slug also helps manage backward compatibility efficiently.

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [January 26, 2026, 9:57pm UTC](https://community.make.com/t/wordpress-custom-api-slug/94716/4 "2026-01-26T21:57:06Z")

</div>

This topic was automatically closed because it's resolved or inactive. Please, start a new topic.


