Default API endpoints in Wordpress - Step-by-Step Execution

Concept Flow - Default API endpoints

WordPress Site

↓

REST API Initialized

↓

Default Endpoints Registered

↓

Client Sends HTTP Request

↓

Endpoint Matches Request

↓

Process Request & Return JSON Response

↓

Client Receives Data

WordPress sets up default REST API endpoints that listen for HTTP requests and return JSON data automatically.

Execution Sample

Wordpress

GET /wp-json/wp/v2/posts
GET /wp-json/wp/v2/pages
GET /wp-json/wp/v2/users

These are example HTTP GET requests to default WordPress REST API endpoints to fetch posts, pages, and users.

Execution Table

Step	Action	Request URL	Endpoint Matched	Response Type	Result
1	Client sends HTTP GET	/wp-json/wp/v2/posts	/wp/v2/posts	JSON	List of posts returned
2	Client sends HTTP GET	/wp-json/wp/v2/pages	/wp/v2/pages	JSON	List of pages returned
3	Client sends HTTP GET	/wp-json/wp/v2/users	/wp/v2/users	JSON	List of users returned
4	Client sends HTTP GET	/wp-json/wp/v2/comments	/wp/v2/comments	JSON	List of comments returned
5	Client sends HTTP GET	/wp-json/wp/v2/nonexistent	No match	404 Error	Endpoint not found
6	Client sends HTTP POST	/wp-json/wp/v2/posts	/wp/v2/posts	JSON	New post created (if authorized)
7	Client sends HTTP GET	/wp-json/	Root API	JSON	API index with available namespaces
8	Client sends HTTP GET	/wp-json/wp/v2/	/wp/v2 root	JSON	List of available routes in wp/v2 namespace

💡 Requests to unknown endpoints return 404; authorized POST requests create or update data.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 5	After Step 6
Request URL	None	/wp-json/wp/v2/posts	/wp-json/wp/v2/pages	/wp-json/wp/v2/users	/wp-json/wp/v2/nonexistent	/wp-json/wp/v2/posts
Endpoint Matched	None	/wp/v2/posts	/wp/v2/pages	/wp/v2/users	No match	/wp/v2/posts
Response	None	Posts JSON	Pages JSON	Users JSON	404 Error	Post Created JSON

Key Moments - 3 Insights

Why does a request to /wp-json/wp/v2/nonexistent return a 404 error?

Because there is no default endpoint registered for 'nonexistent', so the API returns a 404 as shown in execution_table step 5.

Can you create a new post by sending a GET request to /wp-json/wp/v2/posts?

No, GET requests only fetch data. Creating a post requires a POST request as shown in step 6.

What does the root API endpoint /wp-json/ return?

It returns a JSON index of available namespaces and routes, helping clients discover API endpoints, as in step 7.

Visual Quiz - 3 Questions

Look at the execution_table, what response does the client get when requesting /wp-json/wp/v2/users?

A A list of users in JSON format

B A 404 error

C A list of posts

D An HTML page

💡 Hint

Check execution_table row 3 under 'Response Type' and 'Result'

At which step does the API return a 404 error?

A Step 2

B Step 6

C Step 5

D Step 1

💡 Hint

Look for '404 Error' in the 'Response Type' column in execution_table

If the client sends a POST request to /wp-json/wp/v2/posts, what happens according to the execution_table?

A A list of posts is returned

B A new post is created if authorized

C A 404 error is returned

D Nothing happens

💡 Hint

See step 6 in execution_table under 'Action' and 'Result'

Concept Snapshot

WordPress default API endpoints are URLs like /wp-json/wp/v2/posts.
They respond to HTTP requests with JSON data.
GET requests fetch data; POST requests create or update data.
Unknown endpoints return 404 errors.
The root /wp-json/ shows available API namespaces.

Full Transcript

WordPress automatically sets up default REST API endpoints under the /wp-json/ URL. When a client sends an HTTP request like GET /wp-json/wp/v2/posts, WordPress matches this to the posts endpoint and returns a JSON list of posts. Similarly, requests to pages, users, and comments endpoints return their respective data. If the client requests an endpoint that does not exist, such as /wp-json/wp/v2/nonexistent, the API returns a 404 error. POST requests to endpoints like /wp-json/wp/v2/posts can create new content if the client is authorized. The root API endpoint /wp-json/ returns a JSON index of available namespaces and routes to help clients discover the API. This flow ensures WordPress sites provide a standard way to access and manipulate site data via HTTP requests.

Practice

1. What is the main purpose of WordPress default API endpoints?

easy

A. To allow easy access to WordPress data via URLs

B. To create custom themes automatically

C. To manage user roles and permissions

D. To optimize website SEO settings

Solution

1. Step 1: Understand what API endpoints do

   API endpoints provide a way to get or send data through URLs.

2. Step 2: Identify the role of default WordPress endpoints

   They let you access WordPress content like posts or users easily without extra coding.

3. Final Answer:

   To allow easy access to WordPress data via URLs -> Option A

4. Quick Check:

   Default API endpoints = easy data access [OK]

Hint: Default API endpoints = easy data access URLs [OK]

Common Mistakes:

• Thinking endpoints create themes
• Confusing endpoints with user management
• Assuming endpoints handle SEO

2. Which of the following is the correct default REST API endpoint URL to get all posts in WordPress?

easy

A. /wp-content/posts

B. /wp-admin/posts

C. /api/v1/posts/all

D. /wp-json/wp/v2/posts

Solution

1. Step 1: Recall the WordPress REST API base URL

   The base URL for WordPress REST API is /wp-json/wp/v2/.

2. Step 2: Identify the correct endpoint for posts

   The posts endpoint is posts, so full URL is /wp-json/wp/v2/posts.

3. Final Answer:

   /wp-json/wp/v2/posts -> Option D

4. Quick Check:

   Posts endpoint = /wp-json/wp/v2/posts [OK]

Hint: WordPress REST API base = /wp-json/wp/v2/ [OK]

Common Mistakes:

• Using admin URLs instead of API URLs
• Confusing API version or path
• Using incorrect folder paths

3. What will be the result of accessing the URL /wp-json/wp/v2/posts/10 in a WordPress site?

medium

A. Returns the post with ID 10 in JSON format

B. Returns a list of all posts except post 10

C. Returns an error because ID is not allowed

D. Redirects to the homepage

Solution

1. Step 1: Understand the endpoint pattern

   The URL /wp-json/wp/v2/posts/{id} fetches a single post by its ID.

2. Step 2: Interpret the given URL

   Here, ID is 10, so it returns the post with ID 10 in JSON format.

3. Final Answer:

   Returns the post with ID 10 in JSON format -> Option A

4. Quick Check:

   Single post URL returns that post [OK]

Hint: URL with /posts/{id} returns that post [OK]

Common Mistakes:

• Thinking it returns all posts except one
• Assuming ID is invalid in URL
• Expecting a redirect instead of JSON

4. You try to fetch users data using /wp-json/wp/v2/users but get a 401 Unauthorized error. What is the likely cause?

medium

A. The URL is missing the API version

B. The users endpoint does not exist in WordPress

C. You need proper authentication to access users endpoint

D. You must use GET method instead of POST

Solution

1. Step 1: Check endpoint access rules

   Users endpoint requires authentication because user data is sensitive.

2. Step 2: Analyze the error 401 Unauthorized

   This error means the request lacks valid credentials to access the resource.

3. Final Answer:

   You need proper authentication to access users endpoint -> Option C

4. Quick Check:

   401 error = authentication needed [OK]

Hint: 401 error means login/auth needed [OK]

Common Mistakes:

• Thinking users endpoint is missing
• Assuming URL version is wrong
• Confusing HTTP methods

5. You want to get all published posts with the category ID 5 using the default WordPress REST API. Which URL should you use?

hard

A. /wp-json/wp/v2/posts?category=5&status=published

B. /wp-json/wp/v2/posts?categories=5&status=publish

C. /wp-json/wp/v2/posts?cat=5&post_status=publish

D. /wp-json/wp/v2/posts?categories=5&post_status=published

Solution

1. Step 1: Identify correct query parameters for category and status

   WordPress REST API uses categories for category IDs and status for post status.

2. Step 2: Match parameters with correct values

   Category ID is 5, and published posts use status=publish.

3. Final Answer:

   /wp-json/wp/v2/posts?categories=5&status=publish -> Option B

4. Quick Check:

   categories=5 and status=publish are correct params [OK]

Hint: Use categories=ID and status=publish for filtering posts [OK]

Common Mistakes:

• Using wrong parameter names like category or cat
• Using status=published instead of publish
• Mixing post_status with status