Reminder: Some Open API v2 data requirements are changing on April 1

[Etsy Developer Community]

Hello again, 

A couple of weeks ago, we got in touch to let you know about data requirement changes in Etsy’s Open API v2. This is a reminder that starting April 1, Etsy will require requests to create or save changes to a listing or a shipping profile to provide certain fulfillment data needed to calculate an Estimated Delivery Date. We’re doing this to ensure that Open API v2 is in line with the Etsy web experience.

What is an Estimated Delivery Date? We use fulfillment data to calculate an estimated delivery date for shoppers on Etsy. This lets customers know when their order is expected to arrive—a key piece of information they look for when shopping on Etsy.

Generally, the estimated delivery date is based on a combination of the processing time, transit time*, and origin location data. These factors inform what data we require. 

What's changing? Starting April 1, in order to save changes to a listing or a shipping profile via Open API v2, certain fulfillment data on shipping profiles will be required.

The following routes are affected:

createListing

• HTTP Method and URI: POST /listings
• Newly Required Data: shipping_template_id 
  • If the shipping template you're attaching to this listing or any of its entries and upgrades is missing required data, the listing create request will fail.
    
  • Update the relevant shipping data before attempting to create a listing.
    

updateListing

• HTTP Method and URI: PUT /listings/:listing_id
  
• Newly Required Data:
  • If the shipping template attached to this listing or any of its entries and upgrades are missing any required data, the listing update request will fail.

  • Update the relevant shipping data before attempting to update a listing.

createShippingInfo

• HTTP Method and URI: POST /listings/:listing_id/shipping/info
  
• Newly Required Data:
  • min_processing_days
  • max_processing_days
  • origin_postal_code
  • transit time data*

updateShippingInfo

• HTTP Method and URI: PUT /shipping/info/:shipping_info_id
  
• Newly Required Data:
  • If any of the data required to create a ShippingInfo record is not already stored on the record you're updating, the request will fail. 
  • Provide the missing data in the update request if it doesn't already exist. 
    

createShippingTemplate

• HTTP Method and URI: POST /shipping/templates
  
• Newly Required Data:
  • min_processing_days
  • max_processing_days
    
  • origin_postal_code
    
  • transit time data*
    

updateShippingTemplate

• HTTP Method and URI: PUT /shipping/templates/:shipping_template_id
• Newly Required Data: transit time data*

createShippingTemplateEntry

• HTTP Method and URI: POST /shipping/templates/entries
• Newly Required Data: transit time data*

updateShippingTemplateEntry

• HTTP Method and URI: PUT /shipping/templates/entries/:shipping_template_entry_id
• Newly Required Data: transit time data*

createListingShippingUpgrade

• HTTP Method and URI: POST /listings/:listing_id/shipping/upgrades
  
• Newly Required Data: transit time data*

updateListingShippingUpgrade

• HTTP Method and URI: PUT /listings/:listing_id/shipping/upgrades
• Newly Required Data: transit time data*

createShippingTemplateUpgrade

• HTTP Method and URI: POST /shipping/templates/:shipping_template_id/upgrades
• Newly Required Data: transit time data*

updateShippingTemplateUpgrade

• HTTP Method and URI: PUT /shipping/templates/:shipping_template_id/upgrades
  
• Newly Required Data: transit time data*

* We can derive transit times with two different sets of data, so "transit time data" is defined as a combination of shipping_carrier_id and mail_class OR a combination of min_delivery_time and max_delivery_time

If you don't provide the data listed above in listing and shipping endpoints by April 1, your requests to update listings and shipping data will fail. We wanted to let you know so that you can account for these requirements in your product as needed.

Update your app

These required fields are already available to you, so you can start sending this data in your API requests right away. 

We plan to officially sunset Open API v2 in the second half of 2022. You can learn more about that timeline and migrating to Etsy's Open API v3 here. We plan to include these same requirements in Open API v3  and will share the details in the coming months.

Got questions? 

We have answers. We’ll continue to share updates on the Open API v2 site.

[Anıl U.]

How to define v3 oauth2 in php. Is there an example as curl?

1 Mart 2022 Salı tarihinde saat 16:57:05 UTC+3 itibarıyla Etsy Developer Community şunları yazdı: