Why is the Payouts API returning a 404 error?

AshwiniSharma
Shopify Partner
23 0 6

Hello,

I am trying to hit the /shopify_payments/payouts.json API for my shopify store but I am getting a 404 error from the API. I want to know the reason for the API giving 404 as the URL is correct and other Shopify APIs are giving responses from the same URL. The example URL that I am using is - 
https://{shopify_shop_name}.myshopify.com/admin/api/2023-04/shopify_payments/payouts.json?limit=1

Please mention if there is anything that I am doing wrong or any concept that I am missing.

Also, I have checked from the scopes and the concerned scope, that is, read_shopify_payments_payouts has been added to the particular API client. Is the API giving 404 in case of no data?

Replies 9 (9)

karanQode
Shopify Partner
12 0 2

A 404 error from an API indicates requested resource was not found on the server.

-Make sure that you've correctly replaced {shopify_shop_name} with the actual name of your Shopify store in the URL.
-Ensure that you're using the correct API version (2023-04) and the correct endpoint (/shopify_payments/payouts.json).

-Also you can check the scopes you define to access the apis

AshwiniSharma
Shopify Partner
23 0 6

Hello @karanQode 

- I checked that the shop_name was correct as other endpoints are working fine.

- The API version and the endpoint are correct.

- Also checked the scopes and the scopes are also correct. I verified this as for another shop name with the same set of scopes the same API is working fine.

Is there anything else that I should check for this error.

Novtopro
Shopify Partner
2 0 1

Hi, I have the same issue here. 

- request:
    method: get
    uri: https://sourcingforce.myshopify.com/admin/api/2023-04/shopify_payments/payouts.json?date_max=2023-09-16&date_min=2023-09-15&limit=250
    body:
      encoding: UTF-8
      base64_string: ''
    headers:
      X-Shopify-Access-Token:
      - REPLACED_FOR_SECURITY_REASONS
      Content-Type:
      - application/json
      Connection:
      - close
      Host:
      - sourcingforce.myshopify.com
      User-Agent:
      - http.rb/5.1.1
  response:
    status:
      code: 404
      message: Not Found
    headers:
      Date:
      - Wed, 11 Oct 2023 02:27:55 GMT
      Content-Type:
      - text/html
      Transfer-Encoding:
      - chunked
      Connection:
      - close
      X-Sorting-Hat-Podid:
      - '294'
      X-Sorting-Hat-Shopid:
      - '74328703271'
      
AshwiniSharma
Shopify Partner
23 0 6

Hello @Novtopro @karanQode 
Is this issue resolved for you? Are you still facing 404 in case of Payout endpoints? I have checked the things @karanQode mentioned, the scopes are assigned correctly, the shop name and version are also correct. Is there anything else that I am missing here? Or it is giving 404 for everyone in case of No Data?

Novtopro
Shopify Partner
2 0 1
Yes, still facing the error. Can’t figure out that’s the root cause.
ben_storefeed
Shopify Partner
2 0 1

I'm running into the same thing, any updates here, were you able to work around it?

steamroller
Shopify Partner
8 0 3

Apparently if {shopify_shop_name} is a sandbox with no data a 404 is returned.  404 is not the proper response.  A response 200 with [] is the proper response.  It's unclear how a sandbox can mock this data.  Shopify needs to address this.

eribe89
Shopify Partner
3 0 0

Hi !! With "is a sandbox" you mean a test shop?
Because i'm having the same issue, and i'm developing in a testing store.
I only added the scope shopify_payments_payouts because shopify_payments throws error (that two scopes is what the documentation said is needed).

Are you using the same scope? did it work for someone with test store? (i did fictional payments)

JayateerthD
Shopify Partner
1 0 0

This is a very illogical situation created by Shopify. As you are testing this endpoint, and you are using a testing store, there would be no transactions from Shopify to your Bank Account. Thus, it should give a reply as an empty object with a 200 OK response, instead it gives 404 Error, which is so much annoying.

I hope this helps you understand this issue