Main issue: POST/PUT requests to the carrier_services endpoint return errors, while GET requests succeed.
Initial state: PUT/POST returned 404. The app reportedly has both Read and Write shipping permissions. The user discovered their endpoint was behind a store password and asked how to make it public.
Clarification: A responder noted a password block would not typically produce a 404 and requested the full POST/PUT URL for diagnosis.
Latest update: After making the endpoint publicly accessible, attempts to create a carrier service from the server now return 400 Bad Request.
The user triggers creation via a frontend call to a backend “/add” route. Code samples and console output are provided as images, which are central to understanding the request payload/headers.
Status and next steps:
No confirmed solution yet; the issue shifted from 404 to 400 after removing password protection.
Pending details include the exact URL being used and verification of the request body and headers shown in the screenshots. The discussion remains open.
Summarized with AI on February 28.
AI used: gpt-5.
Hi , im having this 404 error when i make a PUT or POST request to carrier_services but if i make GET request to get a list of carrier services retrun data successfully
Could you please provide the full URL of the endpoint you’re trying to POST/PUT to? If it was blocked by a password, it wouldn’t be returning a 404 response.
when i made get request from frontend to my (“/add”) get request to create new carrier service with REST api provided by shopify api it return error 400 bad request