Convo API

[Tom Anderson]

I believe we as developers should have access to send email on an OAuth'ed user's behalf.  I know of one app already sending convos by proxy but it's not in the API yet.  Here is my interpretation of it's implementation:

1. Add a new convo_w permission scope

2. Add a new method to the new Convo API
    Method Name: send
    Synopsis: Attempt to send a convo by proxy
    HTTP Method: POST
    URI: __SELF__/convos (note this is not __SELF__/convos/{target_user_id}  I don't think developers should need to modify an API URL per request changing instead only the parameters.)
    Parameters:
        target_user_id Required type int
        subject Required type string
        body Required type string (allow html?)   
    Requires OAuth: Y
    Permission Scope: convo_rw
    Failure Codes:
        a. No target user id, subject or body
        b. Body exceeds 16k

Tom

[Kelly Neddo]

Forgive me for STUMBLING on in - But I was curious after reading some of the developers speaking if there is ANY WAY to make users like myself who did a name change - GET HER MESSAGES? Etsy's Admins told me "Not in the Near Future" and when you click COMPOSE message to Featherswholesale (ERROR) bc you need to know my OLD shop name (username) The Re-directs dont work properly - Feedback pages go to "solkatsupplies" for example. If anyone has plans to correct or fix our major COMPOSE message issues - PLEASE clue me in I am loosing clients in groves.
Kelly Neddo

featherswholesale on Etsy

solkat on Etsy

solkatphotography on etsy

[Tom Anderson]

This doesn't sound like an API issue and would likely be best addressed by an email off the API list.  It's does sound like a development issue to me.  If you're in the know correct me if I'm wrong please.

Tom

p.s.
It sounds like you changed your username and didn't tell your customers.  This points to a reference in the convos table to the username and not the primary key thereby hitting reply would try to reply to the (old) username in the convos.  But that's just a guess.  Good luck.

--
 
 

[Chris Dary]

Hi Tom,

Thanks for the request - it's definitely something we've heard a number of times. There are a lot of considerations to it (things like spam protection, for example), and we're not quite ready to open this up in the short term. 

By the way: if by "sending convos by proxy" you mean through screen scraping or website automation, that's explicitly against our API terms of service (See section 9) and could be a key-revokable offense. Just a heads up, I'd hate to have to do that, and I won't ask you to rat out your friend, but you may want to let them know that if we see it it's very possible we'll revoke their keys and not reissue them depending on context.

Hope this helps,

-Chris

On Sunday, September 30, 2012 2:59:47 PM UTC-4, mead wrote:

[Tom Anderson]

I feel I've bumped into the same frustration I've seen from many other developers on this list with this request.  Specifically I feel this will fall between the cracks because there is no community list of planned and denied suggestions for future improvements such as a bug/request tracker.  And I am taken aback at the immediate jump to a concern about whether I send SPAM or not.

Chris, here's a link to a definition of acting by proxy: http://www.answerbag.com/q_view/441476
To sum up the definitions posted there and to clarify to you my use of the term Proxy I was referring to the ability of sending email from an API user through an OAuthed user to another user.  I offer this definition because I cannot follow the logic jump in my own head of Proxy > TOS violator.

I LOVE Etsy's community centric approach but I don't feel the LOVE from the API yet.  Maybe I'm just too much of a noobe and should settle in to more conversations here before making the same suggestions others have made before me, if I can avoid that.

Tom

--
 
 

[Julian L.]

The sudden availability of shop name changing caused all sorts of problems for us, too, after years of only user_id and user_name. Not surprising to hear that Etsy didn't quite have it straight, either.

--
 
 

[Chris Dary]

Hi Tom,

Thoughts inline.

On Mon, Oct 1, 2012 at 1:12 PM, Tom Anderson <tom.h.a...@gmail.com> wrote:

I feel I've bumped into the same frustration I've seen from many other developers on this list with this request.  Specifically I feel this will fall between the cracks because there is no community list of planned and denied suggestions for future improvements such as a bug/request tracker.  And I am taken aback at the immediate jump to a concern about whether I send SPAM or not.

I absolutely did not mean to suggest you yourself would spam. It's a general concern when opening up the ability to programmatically send content from one person to another.

 

Chris, here's a link to a definition of acting by proxy: http://www.answerbag.com/q_view/441476
To sum up the definitions posted there and to clarify to you my use of the term Proxy I was referring to the ability of sending email from an API user through an OAuthed user to another user.  I offer this definition because I cannot follow the logic jump in my own head of Proxy > TOS violator.

I'm aware what by proxy means. I was not aware what your intentions were when using it. Thank you for clearing that up.

 

I LOVE Etsy's community centric approach but I don't feel the LOVE from the API yet.  Maybe I'm just too much of a noobe and should settle in to more conversations here before making the same suggestions others have made before me, if I can avoid that.

I hope you don't feel that way - we do genuinely appreciate the feedback, and in fact your feedback on Treasuries just today was fantastic.

We're working hard to get the API to a place that everyone's happier with. As a matter of bandwidth, some things have to wait. I spoke more to this here if you haven't seen it: https://groups.google.com/forum/#!topic/etsy-api-v2/v1WmNFO68ZU

Thanks Tom,

-Chris