Production api http code 301

[fenau25]

When switching from sandbox to production, api http code 301.

Request: GetCategorySpecifics

Response: NULL

HTTP INFO:

[url] => https://api.ebay.com/ws/api.dll
[content_type] =>
[http_code] => 301
[header_size] => 210
[request_size] => 3198
[filetime] => -1
[ssl_verify_result] => 0
[redirect_count] => 0
[total_time] => 0.456158
[namelookup_time] => 0.000831
[connect_time] => 0.150237
[pretransfer_time] => 0.306391
[size_upload] => 325
[size_download] => 0
[speed_download] => 0
[speed_upload] => 712
[download_content_length] => 0
[upload_content_length] => 325
[starttransfer_time] => 0.456134
[redirect_time] => 0
[redirect_url] => https://www.ebay.com/n/error
[primary_ip] => 209.140.129.40
[certinfo] => Array
(
)

[primary_port] => 443
[local_ip] => 172.160.10.215
[local_port] => 41808
[http_version] => 2
[protocol] => 2
[ssl_verifyresult] => 0
[scheme] => HTTPS
[appconnect_time_us] => 306345
[connect_time_us] => 150237
[namelookup_time_us] => 831
[pretransfer_time_us] => 306391
[redirect_time_us] => 0
[starttransfer_time_us] => 456134
[total_time_us] => 456158

[five_notch_trading_post]

That call has been deprecated and is no longer supported as per the docs:

Note: The GetCategorySpecifics call is being deprecated. No new features and/or fields will be added to GetCategorySpecifics, and it will no longer be supported after April 20, 2022. eBay recommends that large sellers and developers migrate to the Taxonomy API RESTful methods. 

If it responds differently in sandbox, that only means the underlying code hasn't been updated to match production yet.

You would need to migrate the obtaining of that information to the Commerce Taxonomy REST API operationId: getItemAspectsForCategory