[ANNOUNCE] Listing title validation changes

[jhali...@etsy.com]

Hi all,
Starting next Tuesday, July 5th, when creating and updating
listings titles will have to be less then 140 characters. This is
changed from the current 255 limit to be in line with the new listing
page on www.etsy.com.

Thanks,
Josh

[david olick]

Thanks!  I'll be sure to update our site with this asap. :)

--
You received this message because you are subscribed to the Google Groups "Etsy API V2" group.
To post to this group, send email to etsy-...@googlegroups.com.
To unsubscribe from this group, send email to etsy-api-v2...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/etsy-api-v2?hl=en.

--
David Olick
CTO
Oriku Inc.

[Julian L.]

Are there any plans to add this info to the documentation?

I recall there was a bit of talk about using JSON Schema or something last year.
The Listing resource info http://developer.etsy.com/docs/read/resource_listing has type information, but not the acceptable values for each field. This information is useful, since the only way to probe the limits currently is trial and error either through the API or web interface.

Thanks,
Julian

[GraGra33]

Umm... how about all the other fields - do they come into effect on
the same date for Create/Update?

I'm reading in the forums that some of the new fields are causing
validation errors on the main site when relisting or renewing - will
the update listing have the same validation requirements even though
they're flagged as optional in the API documentation?

G.

On Jun 29, 8:34 am, "Julian L." <jul...@craftcult.com> wrote:
> Are there any plans to add this info to the documentation?
>
> I recall there was a bit of talk about using JSON Schema or something last year.

> The Listing resource infohttp://developer.etsy.com/docs/read/resource_listinghas type information, but not the acceptable values for each field. This information is useful, since the only way to probe the limits currently is trial and error either through the API or web interface.

>
> Thanks,
> Julian
>
>
>
> > Hi all,
> >    Starting next Tuesday, July 5th, when creating and updating
> > listings titles will have to be less then 140 characters. This is
> > changed from the current 255 limit to be in line with the new listing
> > page onwww.etsy.com.
>
> > Thanks,
> > Josh
>
> > --
> > You received this message because you are subscribed to the Google Groups "Etsy API V2" group.
> > To post to this group, send email to etsy-...@googlegroups.com.
> > To unsubscribe from this group, send email to etsy-api-v2...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/etsy-api-v2?hl=en.- Hide quoted text -
>
> - Show quoted text -

[GraGra33]

Just noticed that the new api documentation on Etsy
http://www.etsy.com/developers/documentation/reference/listing does
not contain the new fields image_id(???), who_made, is_supply, &
when_made as per the old API documentation hosted by Mashery
http://developer.etsy.com/docs/read/resource_listing. also the Mashery
documentation doesn't listing the fields in the Listing Data
Definition.

Which is currently correct and when will the new fields be supported?

G.

On Jun 29, 9:30 am, GraGra33 <gragr...@gmail.com> wrote:
> Umm... how about all the other fields - do they come into effect on
> the same date for Create/Update?
>
> I'm reading in the forums that some of the new fields are causing
> validation errors on the main site when relisting or renewing - will
> the update listing have the same validation requirements even though
> they're flagged as optional in the API documentation?
>
> G.
>
> On Jun 29, 8:34 am, "Julian L." <jul...@craftcult.com> wrote:
>
>
>
> > Are there any plans to add this info to the documentation?
>
> > I recall there was a bit of talk about using JSON Schema or something last year.

> > The Listing resource infohttp://developer.etsy.com/docs/read/resource_listinghastype information, but not the acceptable values for each field. This information is useful, since the only way to probe the limits currently is trial and error either through the API or web interface.

>
> > Thanks,
> > Julian
>
> > > Hi all,
> > >    Starting next Tuesday, July 5th, when creating and updating
> > > listings titles will have to be less then 140 characters. This is
> > > changed from the current 255 limit to be in line with the new listing
> > > page onwww.etsy.com.
>
> > > Thanks,
> > > Josh
>
> > > --
> > > You received this message because you are subscribed to the Google Groups "Etsy API V2" group.
> > > To post to this group, send email to etsy-...@googlegroups.com.
> > > To unsubscribe from this group, send email to etsy-api-v2...@googlegroups.com.

> > > For more options, visit this group athttp://groups.google.com/group/etsy-api-v2?hl=en.-Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -

[jhali...@etsy.com]

I am sorry about that, those new fields some how made it into the
documentation before they were ready. There will be a separate
announcement about them in the next few days. They will be optional at
first but eventually required.

On Jun 28, 11:43 pm, GraGra33 <gragr...@gmail.com> wrote:
> Just noticed that the new api documentation on Etsyhttp://www.etsy.com/developers/documentation/reference/listingdoes
> not contain the new fields image_id(???), who_made, is_supply, &

> when_made as per the old API documentation hosted by Masheryhttp://developer.etsy.com/docs/read/resource_listing. also the Mashery

> documentation doesn't listing the fields in the Listing Data
> Definition.
>
> Which is currently correct and when will the new fields be supported?
>
> G.
>
> On Jun 29, 9:30 am, GraGra33 <gragr...@gmail.com> wrote:
>
>
>
> > Umm... how about all the other fields - do they come into effect on
> > the same date for Create/Update?
>
> > I'm reading in the forums that some of the new fields are causing
> > validation errors on the main site when relisting or renewing - will
> > the update listing have the same validation requirements even though
> > they're flagged as optional in the API documentation?
>
> > G.
>
> > On Jun 29, 8:34 am, "Julian L." <jul...@craftcult.com> wrote:
>
> > > Are there any plans to add this info to the documentation?
>
> > > I recall there was a bit of talk about using JSON Schema or something last year.

> > > The Listing resource infohttp://developer.etsy.com/docs/read/resource_listinghastypeinformation, but not the acceptable values for each field. This information is useful, since the only way to probe the limits currently is trial and error either through the API or web interface.

>
> > > Thanks,
> > > Julian
>
> > > > Hi all,
> > > >    Starting next Tuesday, July 5th, when creating and updating
> > > > listings titles will have to be less then 140 characters. This is
> > > > changed from the current 255 limit to be in line with the new listing
> > > > page onwww.etsy.com.
>
> > > > Thanks,
> > > > Josh
>
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "Etsy API V2" group.
> > > > To post to this group, send email to etsy-...@googlegroups.com.
> > > > To unsubscribe from this group, send email to etsy-api-v2...@googlegroups.com.

> > > > For more options, visit this group athttp://groups.google.com/group/etsy-api-v2?hl=en.-Hidequoted text -

[Cameron Henneke]

Any chance the change to 140 character title descriptions can be delayed?  I need to update my code to handle this new requirement.  However, the sandbox has been broken since the API switch so I have not be able to test any of my changes.

The oAuth dance for shop authorization goes one step further now, but it's still broken.  I can get the access token, but when I call:

http://sandbox.openapi.etsy.com/v2/users/__SELF__

I get the following response:

resp:{'status': '404', 'content-length': '45', 'server': 'Apache', 'x-error-detail': 'User with PK user_id = 6325909 does not exist', 'date': 'Tue, 05 Jul 2011 12:19:58 GMT', 'content-type': 'text/plain;charset=UTF-8'}

Thanks,
Cameron

[Aaron Gardner]

Cameron,

As you requested, we will delay changing the API to enforce new
shorter 140 character-length limits, given the OAuth issues in the API
Sandbox.

We are working on the Sandbox OAuth fix now. We will email an
announcement when the fix is live.

The new target date to change the character limits is this Thursday,
July 7th, 2011.

Best regards,
Aaron Gardner
Developer API Team
Etsy.com

[James Lee]

Hi All,

This change was delayed and will go out tomorrow, Thursday, July 14th instead.

Thanks,
James Lee
Etsy.com

[jhalickman]

Sorry for the delay on this. It is now live.

On Jul 13, 10:26 am, James Lee <j...@etsy.com> wrote:
> Hi All,
>
> This change was delayed and will go out tomorrow, Thursday, July 14th instead.
>
> Thanks,
> James Lee
> Etsy.com
>
>
>
>
>
>
>
> On Tue, Jul 5, 2011 at 12:58 PM, Aaron Gardner <agard...@etsy.com> wrote:
> > Cameron,
>
> > As you requested, we will delay changing the API to enforce new
> > shorter 140 character-length limits, given the OAuth issues in the API
> > Sandbox.
>
> > We are working on the Sandbox OAuth fix now. We will email an
> > announcement when the fix is live.
>
> > The new target date to change the character limits is this Thursday,
> > July 7th, 2011.
>
> > Best regards,
> > Aaron Gardner
> > Developer API Team
> > Etsy.com
>

> > On Tue, Jul 5, 2011 at 8:35 AM, Cameron Henneke <came...@etsyonsale.com> wrote:
> >> Any chance the change to 140 character title descriptions can be delayed?  I
> >> need to update my code to handle this new requirement.  However, the sandbox
> >> has been broken since the API switch so I have not be able to test any of my
> >> changes.
>
> >> The oAuth dance for shop authorization goes one step further now, but it's
> >> still broken.  I can get the access token, but when I call:
>
> >>http://sandbox.openapi.etsy.com/v2/users/__SELF__
>
> >> I get the following response:
>
> >> resp:{'status': '404', 'content-length': '45', 'server': 'Apache',
> >> 'x-error-detail': 'User with PK user_id = 6325909 does not exist', 'date':
> >> 'Tue, 05 Jul 2011 12:19:58 GMT', 'content-type': 'text/plain;charset=UTF-8'}
>
> >> Thanks,
> >> Cameron
>

> >> On Wed, Jun 29, 2011 at 11:02 AM, jhalick...@etsy.com <jhalick...@etsy.com>

> >>> > > > > athttp://groups.google.com/group/etsy-api-v2?hl=en.-Hidequotedtext -