Safe methods vs unsafe methods in Rest API - When to Use Which

The Big Idea

What if a simple mistake in your API could accidentally erase important data?

The Scenario

Imagine you have a website where users can view and change their profile information. You try to handle all actions with the same method, mixing viewing and changing data without clear rules.

The Problem

This approach is risky because users might accidentally change data when they only wanted to see it. It also makes it hard to keep track of what actions are safe (just looking) and which ones can cause changes, leading to bugs and security problems.

The Solution

Using safe methods for actions that only read data, and unsafe methods for those that change data, helps keep things clear and secure. It separates viewing from modifying, so accidental changes are avoided and the system behaves predictably.

Before vs After

✗ Before

POST /user/profile  // used for both viewing and updating profile

✓ After

GET /user/profile   // safe method to view
PUT /user/profile   // unsafe method to update

What It Enables

This clear separation allows APIs to be more reliable, secure, and easier to maintain, making sure data changes happen only when intended.

Real Life Example

When you browse products on an online store, the site uses safe methods to show product details without changing anything. When you add a product to your cart, it uses unsafe methods to update your cart data.

Key Takeaways

Safe methods only read data without changing it.

Unsafe methods modify data and can have side effects.

Separating these methods prevents accidental data changes and improves security.