API support for getting user details?
Hi All
I'm playing with some more integration features and I've come
across a bit of a problem.
What I'd like to do is find a way to query by email the number of discussions and state for a given user. Note that I'm using the term 'user' here to refer to anyone who has ever logged a support request.
The API does seem to have support for that but as far as I can tell it's not working (well it works if I put my email in but not if I put one of my customers emails)
What is not working is
https://api.tenderapp.com/<mytendername>/users?auth=<auth>&email=<email>
If I put my email in I get a nice set of user details but if I pull up a email from a recent customer query it's coming up empty (again I'm pretty sure I'm calling it correctly as my email address seems to work fine)
Is there a way to get a list of discussions based on a customer email that I am must missing?
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Justin on 04 May, 2010 11:56 PM
Looks like another area we need to document better. You can use
user_email
to get a list of discussions by an anon user. Note that if the user has an account, you'll probably need to useuser_id
instead.Our API is still a WIP, so if there is anything you think would be useful, let us know.
2 Posted by loghound on 05 May, 2010 05:56 AM
Thanks -- It took a bit of digging to sort out that the URL calls the discussion leaf not users but once I got that sorted out it was all good.
You know what would be great? If the 'read only' key also worked on the JSON api. I'm writing a small web service and it would be nice if people could use it without worrying about the API key being used for evil (I, of course have no evil intents -- It's just something to make people more comfortable sharing their API key)
-John
3 Posted by Justin on 05 May, 2010 06:04 PM
That's one reason we made it easy to regenerate your existing API key. You really should only give your API key to people or sites you trust. Even in the readonly sense (if you were a supporter/admin) , someone would have complete access to your customer data and all your discussions.
With that being said, if this is something that people eventually want, we'll look into adding it.
I've updated the documentation. Also, we have all of our documentation on GitHub if you'd like to take matters into your own hands, otherwise you can let us know if something needs to be corrected or added.
Thanks for the suggestions!
Will closed this discussion on 18 Aug, 2010 10:15 PM.