Topic: Update People not updating

Hi,

I am having the exact same problem. Have either of you found a solution?

Thank you.

Topic: Update People not updating

Same problem, updating a person using a Put always adds items inside <contact-data> email addresses etc, it doesnt change what is there, here is a full xml for put

objSvrHTTP.Open "PUT", txtURL & "/people/" & Trim(txtPersonId), False, CStr(txtUserName), CStr(txtPassword)
objSvrHTTP.setRequestHeader "Accept", "application/xml" 
objSvrHTTP.setRequestHeader "Content-Type", "application/xml"

I would like to get this working properly for my highrise api article at
http://www.databasejournal.com/features/msaccess/article.php/3745456

Topic: Search By Email Address

Good news! We just pushed support for advanced search by email, both via the web interface and the API. The API documentation has been updated to reflect this:

http://developer.37signals.com/highrise

Topic: Search By Email Address

Though currently undocumented, you can search for additional fields using the ‘criteria’ parameter like so:

/parties/search.xml?criteria[phone]=123
/parties/search.xml?criteria[state]=IL

They can also be combined to narrow the results:

/parties/search.xml?criteria[state]=IL&criteria[zip]=60622

You can’t search by email at this time.

Topic: Search By Email Address

I’m discovering Highrisehq API and I’ve not been able to search people by email address or phone number.
This should be the first step for you to check if a customer already exists.

My understanding of API is that the request bellow is only working for some fields :
curl -u token:X https://subdomain.highrisehq.com/people.xml?title=CEO

It does work for title but it doesn’t for id, last-name , zip or city.
For id, it might come from the fact an id field is stored as an integer and maybe this should be reflected in query.
For other fields, I don’t have a good explaination, at the moment.

How did you query email address ?

Topic: Search By Email Address

I cant find a place in the UI or in the API to search for a person by email address. Im building a zen cart module to save out customers to highrise and there is really no way for me to use the “update” command reliably without a unique identifier of some sort. I figured email address would be a great way to go but i cant find a way to do that anywhere. Anyone have any ideas? Basically when a user registers on my site i want to query highrise using their email address to see if they exist already, if they dont, create a new contact, otherwise update the existing. Thanks!
brian

Topic: Mistakes in the API documentation

I agree that the documentation should be QA’d as thoroughly as the product. Perhaps 37S can make use of its adoring fans to divide up the reference and polish it. One mechanism would be a private wiki until 37S was comfortable with the state of things, then convert it to static web pages (as it is now).

One more: on the page http://developer.37signals.com/highrise/reference.shtml, note the first line: “Data Reference The following sections describe the different data types used by the Basecamp API.”

Cheers

Topic: Mistakes in the API documentation

Sorry to butt in on this, but with all due respect, Reaction couldn’t be more on-target here; as someone looking into the API pretty heavily, those ‘commas and spelling mistakes’ make the difference between a one hour coding session and an eight hour coding session. Reaction’s work is not to be underrated at all; I’d say his criticism was, if anything, restrained. Now that we are in mid-July, what are people thinking of the documentation, is it fully up to snuff? I’m trying to decide if my big project is going to include a highrise API or not.

Topic: Mistakes in the API documentation

Thanks, Skittles. Updated that.

Topic: Mistakes in the API documentation

BTW, I fixed the calls for “List Upcoming For Subject”. The API was right, but the code was wrong. This fix has been deployed.

Topic: Mistakes in the API documentation

Data reference

Wrong:
<contact-data>
<web-addresses>
<web-address>
<id type="integer">1</id>
<address>http://www.example.com</address>
<location>#{ Work || Personal || Other }</location>
</web-address>
</web-addresses>
</contact-data>

Right:
<contact-data>
<web-addresses>
<web-address>
<id type="integer">1</id>
<url>http://www.example.com</url>
<location>#{ Work || Personal || Other }</location>
</web-address>
</web-addresses>
</contact-data>

Topic: Mistakes in the API documentation

I appreciate the work you’re putting into helping us proof-read the API pages. But perhaps it’s a little strong saying that you have to “fix” our API to use it. You’re helping us getting commas right and fixing spelling mistakes, not rewriting the novel. That’s definitely important too, but I would contend that the novel is still quite readable despite it.

In any case, thanks again for your work on this. I’ll continue to update the pages with your corrections.

Topic: Mistakes in the API documentation

I’ve updated the documentation on the live site now. The /users/1.xml example is correct, though. There is both /people and /users on Highrise. Also, the SSL issue is described under Dealing With Failure on the front page.

Thanks for the corrections!

Topic: Mistakes in the API documentation

Hi Reaction,

Thanks for the proof-reading. I’ll incorporate your fixes shortly. Please do keep posting if you find anything else.

Topic: ColdFusion CFHTTP

I’ve posted some simple questions as well. I am hoping someone at 37signals is watching the forums and would get us some answers.