[ANNOUNCE] New API Sandbox
Aaron Gardner
We are pleased to announce a new and improved API Sandbox environment.
We will be switching Sandbox API calls to use this new environment
this coming Monday, June 13, 2011 during business hours (US Eastern
Time Zone). Sandbox API URLs and API keys will stay the same in the
New Sandbox.
The main improvement of the New Sandbox is that its infrastructure has
been upgraded to match the latest production Etsy infrastructure. This
means that all API methods can once again be enabled in the New
Sandbox.
The biggest change for API developers is that New Sandbox will no
longer get any data copied over from the production site or API. It
will start with essentially empty data. API Sandbox developers will
then populate it with test data making Sandbox API calls.
Given this big change, we will begin issuing restricted, read-only
Production API keys along with Sandbox API keys. These read-only keys
will enable you to immediately test read-only API calls against real
data. These restricted keys also have lower rate limits than
full-access production keys. Starting Monday, developers who don't
already have a production API key can obtain a restricted one by
visiting http://developer.etsy.com/apps/mykeys.
We've also automated the dreaded "sandbox user sync." The first time a
new OAuth access token is used in the New Sandbox, its authorized User
resource will be copied to the New Sandbox environment. This will
include the Shop, if the user has one. However, listings from the
user's shop will not be copied. Developers can create listings to test
against in the New Sandbox using the appropriate API methods.
Note that ID numbers in the New Sandbox will not match ID numbers in
production. New Sandbox data will be completely separate and
independent of production data.
We will update the API documentation to reflect these changes when the
New Sandbox environment goes live on Monday.
These changes are just the first phase of Sandbox improvements. Future
changes will give API developers more tools to create test data in the
New Sandbox environment, including eventually a Sandbox-specific web
UI just for API developers similar to the main site. Stay tuned!
Best regards,
Aaron Gardner
Developer API Team
Etsy.com
Lior Sion
a temporary key instead of the sandboxed one? My calls are read only
and I can't use the empty sandbox..
On Jun 11, 12:27 am, Aaron Gardner <agard...@etsy.com> wrote:
> Hi All,
>
> We are pleased to announce a new and improved API Sandbox environment.
>
> We will be switching Sandbox API calls to use this new environment
> this coming Monday, June 13, 2011 during business hours (US Eastern
> Time Zone). Sandbox API URLs and API keys will stay the same in the
> New Sandbox.
>
> The main improvement of the New Sandbox is that its infrastructure has
> been upgraded to match the latest production Etsy infrastructure. This
> means that all API methods can once again be enabled in the New
> Sandbox.
>
> The biggest change for API developers is that New Sandbox will no
> longer get any data copied over from the production site or API. It
> will start with essentially empty data. API Sandbox developers will
> then populate it with test data making Sandbox API calls.
>
> Given this big change, we will begin issuing restricted, read-only
> Production API keys along with Sandbox API keys. These read-only keys
> will enable you to immediately test read-only API calls against real
> data. These restricted keys also have lower rate limits than
> full-access production keys. Starting Monday, developers who don't
> already have a production API key can obtain a restricted one by
Aaron Gardner
Yes. In addition to your existing API Sandbox key you will be able to
get a restricted production key here:
http://developer.etsy.com/apps/mykeys
We will send out additional announcements when the new API Sandbox is
up and the new keys can be obtained.
Best regards,
Aaron Gardner
Developer API Team
Etsy.com
> --
> 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.
>
>
Aaron Gardner
2011 -- instead of today.
Thank you for your patience.
Best regards,
Aaron Gardner
Developer API Team
Etsy.com
Lior Sion
Aaron Gardner
See the original announcement for details:
http://developer.etsy.com/New_API_Sandbox
There is one additional temporary change: the Team resource methods
are temporarily disabled in the New Sandbox while we troubleshoot an
issue. Team methods still work normally in the production API.
Thanks,
Aaron Gardner
Developer API Team
Etsy.com
GraGra33
through renew/changes? Will we be able to toggle the listing state in
the sandbox to all states for test purposes?
G.
On Jun 11, 7:27 am, Aaron Gardner <agard...@etsy.com> wrote:
> Hi All,
>
> We are pleased to announce a new and improved API Sandbox environment.
>
> We will be switching Sandbox API calls to use this new environment
> this coming Monday, June 13, 2011 during business hours (US Eastern
> Time Zone). Sandbox API URLs and API keys will stay the same in the
> New Sandbox.
>
> The main improvement of the New Sandbox is that its infrastructure has
> been upgraded to match the latest production Etsy infrastructure. This
> means that all API methods can once again be enabled in the New
> Sandbox.
>
> The biggest change for API developers is that New Sandbox will no
> longer get any data copied over from the production site or API. It
> will start with essentially empty data. API Sandbox developers will
> then populate it with test data making Sandbox API calls.
>
> Given this big change, we will begin issuing restricted, read-only
> Production API keys along with Sandbox API keys. These read-only keys
> will enable you to immediately test read-only API calls against real
> data. These restricted keys also have lower rate limits than
> full-access production keys. Starting Monday, developers who don't
> already have a production API key can obtain a restricted one by
GraGra33
seeing a "ERR_400_MISSING_REQUIRED_CONSUMER_KEY" even though the key
is passed.
A private email has been sent with the specifics...
Please advise if the READONLY live api keys allow for private calls to
access private data that's no longer available in the Sandbox.
G.
>
> - Show quoted text -
Aaron Gardner
was just a case of "API key/endpoint mismatch" which just means a
restricted production API key was incorrectly used with the sandbox
endpoint.
To clarify: production API keys, whether they are restricted or
full-access, will only work with the production API base endpoints:
- http://openapi.etsy.com/v2/public/
- http://openapi.etsy.com/v2/private/
Best regards,
Aaron Gardner
Developer API Team
Etsy.com
GraGra33
pulling across all the User, Profile and Shop data - not all fields
are filled - eg: is_seller = false when the user has a shop and shop
data was transfered and can be found on the Sandbox.
Is this the correct behavior? Can you please identify what resources
and what fields we're supposed to be seeing?
Thanks,
Aaron Gardner
The field is_seller should be copied. We are investigating. We will
also improve the documentation about the fields that are copied.
Not all fields are intended to be copied to the new Sandbox, but keep
in mind we are planning to provide a more complete web UI solution for
Sandbox data in the future.
Are there other specific fields besides is_seller that you feel should
be copied to the new Sandbox that currently are not?
Best regards,
Aaron Gardner
Developer API Team
Etsy.com
GraGra33
How much? All fields and resources that we cannot generate using the
API. It's a real juggle and huge overhead to develop on the new Sandox
+ Limited Live Read Only API when IDs don't match and what's been
moved to the Sandbox is incomplete.
Can we bring back the old system please...
G.