Types of API Endpoints and How to Customize Requests

Understanding the types of API endpoints is essential when building apps that interact with external services. In this post, we break down the different types—GET, POST, PUT, DELETE—and show how to use them with request bodies and query parameters using JavaScript’s fetch() API.

What Are API Endpoints?

An API (Application Programming Interface) allows two software applications to talk to each other, and API endpoints are the specific URLs where this interaction happens. Each endpoint performs a particular action, whether retrieving data, creating a new record, or deleting something from a database.

For example, a CRM might expose an endpoint like https://api.example.com/contacts to allow access to contact data. These interactions are powered by HTTP methods, most commonly the following four endpoint types:

• GET – Retrieve data
  
• POST – Create new data
  
• PUT – Update existing data
• DELETE – Remove data

Common Types of API Endpoints

These four types of API endpoints represent the standard CRUD operations—Create, Read, Update, Delete. Here's how they work and how to use them in JavaScript with the fetch() API.

GET Endpoints

GET endpoints are used to retrieve information from an API. They are the most commonly used type of endpoint and are used to retrieve data such as user information, product details, and more.

For example, let's say you want to retrieve the details of a specific product from an e-commerce API using JavaScript's fetch API. You would use the following code:

fetch("https://api.example.com/products/123", { method: "GET" })
  .then((response) => response.json())
  .then((data) => {
    console.log(data);
  });

This sends a GET request to the products/123 endpoint and returns product details in JSON format.

POST Endpoints

POST endpoints are used to send new information to an API. They are commonly used to create new resources such as creating a new user or a new product.

‍

For example, let's say you want to create a new product in an e-commerce API using JavaScript's fetch API. You would use the following code:

const product = {
  name: "Product Name",
  description: "Product Description",
  price: 100,
};

fetch("https://api.example.com/products", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify(product),
})
  .then((response) => response.json())
  .then((data) => {
    console.log(data);
  });

In this example, we're using the fetch API to send a POST request to the endpoint "https://api.example.com/products" and include the product details in the request body in the form of JSON.

This creates a new product and returns confirmation.

PUT Endpoints

PUT endpoints are used to update existing information in an API. They are similar to POST endpoints but are used to update resources instead of creating new ones.

For example, let's say you want to update the details of a specific product in an e-commerce API using JavaScript's fetch API. You would use the following code:

const updatedProduct = {
  name: "New Product Name",
  description: "New Product Description",
  price: 120,
};

fetch("https://api.example.com/products/123", {
  method: "PUT",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify(updatedProduct),
})
  .then((response) => response.json())
  .then((data) => {
    console.log(data);
  });

This updates product 123 with new information.

DELETE Endpoints

DELETE endpoints are used to remove resources from the system.

For example, let's say you want to delete a specific product from an e-commerce API using JavaScript's fetch API. You would use the following code:

fetch("https://api.example.com/products/123", { method: "DELETE" })
  .then((response) => response.json())
  .then((data) => {
    console.log(data);
  });

This sends a DELETE request to remove the product with ID 123.

Using Request Body and Query Parameters

In addition to understanding the different types of API endpoints, it’s equally important to know how to customize your requests using query parameters and the request body. These tools give you more control over how data is fetched or sent, allowing you to filter results, send structured data, or update only what’s necessary.

Query Parameters

These are appended to the URL to filter or sort results, often used with GET requests.

fetch(`https://api.example.com/products?category=books&price=50-100`, {
  method: "GET",
})
  .then((response) => response.json())
  .then((data) => {
    console.log(data);
  });

• ? starts the query
• & separates multiple parameters

Request Body

Used with POST and PUT endpoints to send structured data (often JSON). This data is passed via the body key in your fetch configuration.

API Endpoints in Real-World Scenarios

How Noloco Helps You Work with APIs

Noloco makes it easy to integrate and interact with APIs, no backend or advanced technical skills required. Whether you're a business analyst or operations manager, you can connect to external APIs and trigger actions directly from your custom apps.

Here’s what you get with Noloco:

• API Workflows – Trigger GET, POST, PUT, DELETE actions via our AI-powered workflow builder
  
• Permissions & Access Control – Secure your API access with our advanced permissions system
  
• Customizable Interface – Use our point-and-click app builder to design the perfect frontend for your internal or external API use case
  
• Integrated Data Sources – Pull data from Airtable, SQL, or our own Noloco Tables

Need help building your API-connected app? Hire a Noloco Expert

FAQs About the Types of API Endpoints

What are the different types of API endpoints?

The most common types are:

• GET – Retrieve data
  
• POST – Create data
  
• PUT – Update existing data
  
• DELETE – Remove data
  

What’s the difference between query parameters and request body?

• Query parameters are used in the URL (usually for filtering GET requests).
  
• Request bodies contain the data being sent (used in POST and PUT).
  
  

Can I use API endpoints without a backend?

Yes. With platforms like Noloco, you can trigger API calls directly from the frontend via workflows, ideal for teams without in-house developers.

What are some other resources related to API endpoint types?