How to show JSON response after changing the HTTP method or Request type in postman?

Well, your API should have an endpoint that 'listens' for GET requests to the /login route. You can send a response from that endpoint.

Route::get('/login', function() { /** send response */ }); / but this is usually a login page endpoint
Route::post('/login', function() { /** login logic */ });

@takdw then what if I have 100 APIs.?

Hmm... Do you want to send an error response when the app/users hit an endpoint that is not available (or if they access it using the wrong RequestType)? If so, you can add a general catch rule for requests that do not match any other rules. It will take the form of something like this:

routes/api.php or routes/web.php

// All your other rules
Route::post('/login', 'AuthController@store');
// ...

// Anything else, throw a 404 error
Route::get('/{any}', function () {
    $data = [
        'error' => [
            'message' => 'Unknown endpoint'.
            'statusCode' => 404
        ]
    ];
    return Response::json($data, 404);
})->where('any', '.*');

I believe something like this should work.

@takdw here is my question https://stackoverflow.com/questions/53393308/laravel-how-to-show-json-response-after-changing-http-method-in-postman

@SHASHI_VERMA - @shashi_verma I looked at the question on StackOverflow. I'll just answer it here.

You have a POST /auth/signup endpoint in your api.php file. This endpoint is responsible to respond to POST requests only. But here you are sending a GET request to the endpoint. The thing is POST /auth/signup and GET /auth/signup are two different endpoints. The GET endpoint can not respond to POST requests and vice versa. This is clearly evident in the error Laravel is throwing when you try to hit /auth/signup as a POST request: MethodNotAllowedException.

Like I have stated in my previous post, you have to create an endpoint that catches any routes that couldn't be matched. Add the GET route I defined in my previous reply at the end of your api.php file and try it. You should get a 404 Error response in JSON format.

@takdw I did the same as you can see there, it doesn't work with the APIs endpoints