Topic: Highrise API / Search By Email Address

What we did is search by last name, and then search the results to match an email address.

This method works in our case, where we have someone supplying full contact information, and we want to test for an exisiting entry. It is of course an imperfect solution, since it relies on the last names matching (exactly, but I suppose we could just offer 3-4 letters to widen the test).

I think it’s disappointing something seemingly as simple as this is not offered. Email address is one of the best unique identifiers, and a simple select by email match should be straight-forward.

Topic: Highrise API / Update People not updating

Are there any thoughts on why this isn’t working?

We are putting the finishing touches on a commercial real estate site for a few thousand users that will be upselling Highrise, but only if we can get this interaction working. It is meant to be a solution for brokers who do not have an existing contact database system.

Topic: Highrise API / Update People not updating

We have been having a problem w/ the Update People call.

Does not work:
<phone-numbers>
<phone-number> <id type="integer">1</id>
<number>303-555-1212</number>
<location>Work</location>
</phone-number>
</phone-numbers>

Does not work:
<phone-numbers>
<phone-number> <id type="integer">5502737</id>
<number>303-555-1212</number>
<location>Work</location>
</phone-number>
</phone-numbers>

If we change the name, company, etc, those work fine. If we leave out the <id type="integer"> we just get a duplicate entry.

(I tried to format the code better but it kept getting fixed after submit)

Topic: Feature Requests / Email when task canceled

A couple of times I have cancled a task I assigned to someone, and the link in the email goes nowhere after that. We then need to exchange emails to clear this up, even when I leave a note.

Please send an email when a task assigned to someone else is canceled, or allow for a page that still has the task, and that it was canceled.

Topic: Feature Requests / Email when task complete

Probably been suggested already, but knwoing when a task is completed that I assigned would be as important as knowing one is assigned to me, and should merit an email.

Topic: Highrise API / Mistakes in the API documentation

I put “fix” in quotes for the very reason of not meaning it explicitly. I was just trying to say that I spend a lot of time taking each call, testing it, and where is doesn’t work, playing w/ it until I find out (hopefully) what is the correct way, and bringing that result back here to post.

While I am just finding spelling errors, these errors are not just grammatical mistakes in a story or novel. These are lines of code that need to be exact in order to work, or they don’t. It’s not like they are just ruining the flow of the dialog in a novel, per se. They make the API unusable unless they are correct.

Again, I am not trying to be hard on anyone, and obviously I am trying to help. Otherwise, I wouldn’t be taking the time to test every single call, and pass these back to you. I would just be noting them locally and moving on. I do want more people to make use of this, because the greater the acceptance, the better the community here. Again, I have just been frustrated because it seems like someone took the time to write all of this, but obviously didn’t test all of it. I know if I had done that, my company and my clients would have equally taken me to task.

Thanks again for the dialog on this. I do appreciate that these are being addressed. I am only 1/2 through the API list (I started at the bottom for whatever reason), so there may be more additions to this list as I finish.

Topic: Feature Requests / Make offsite links tagert="_blank" by default

I already use ctrl + left click to open in a new tab, but it can be a pain to remember to do.

While the majority of sites are same window, I tend to see HR like a fourm or msg board, and in the majority of those, the _blank is a common behavior.

It would be nice if it were an option to turn on is all. I’m not trying to bend everyone’s will/usage.

Topic: Feature Requests / Option to populate contact w/ company info

It would help to have a link in a new contact for a company record where it will fill in the the record w/ the info from the company. It would be much easier to just add directly line, email, etc, and not re-enter things like address over and over.

Topic: Feature Requests / Make offsite links tagert="_blank" by default

When we add a link in a note or comment, or for a web site to a company or person, it would be nice to have that open in a new window instead of taking me away from HR.

Topic: Troubleshooting and Bug Reports / Deleteled comeleted tasks on dash

Don’t know if this is a bug or by design.

If you delete a completed task, it still shows up on the dashboard, where it needs to be deleted separately.

Topic: Highrise API / Mistakes in the API documentation

Thank you David for giving this some attention. I do appreciate it, and it does answer the problem I am having here.

I just have to confess how slow our adaptation of the API is going because there, so far, has not been a single page that is error-free. The only way we currently will be able to begin to offer this product to our clients is by first having me go through each function on at time to find out which work at all, and hopefully when they don’t, can figure out ourselves. Right now, I feel like I am “fixing” your API in order to have the pivilage of using it.

I am not trying to be harsh here, just a little critical and mostly frustrated. I know tech documentation is not fun to do, but you must agree it is critical it be accuarate. I’ve only been slighly more frustrated in that my biz partner read the 37signals book, and mentioned that usability is of utmost importance them. While that is very true of the Highrise product, it has totally broken down as far as programming for it goes.

I will keep posting problems as I find them, and fixes where I can. I hope they can get quick attention on your end, to the benefit of all.

Topic: Highrise API / Mistakes in the API documentation

Tasks (http://developer.37signals.com/highrise/tasks.shtml)

Wrong:
List Upcoming For Subject
GET /companies/#{subject-id}/tasks.xml
GET /kases/#{subject-id}/tasks.xml

Right:
List Upcoming For Subject
Not sure. No variation seemed to work. The path (companies/kases) seem fine. I would suggest personal error, except the /people version works.

Topic: Highrise API / Mistakes in the API documentation

Introduction (http://developer.37signals.com/highrise/index.shtml)

This one I can’t tell if it’s a typo or not. Their examples on how to do things like PUT and DELETE show “http://”. It wasn’t until a lot of trial and error (inspired by the other typos here) I tried “https” and got it work.

I can’t say if this is a typo, or if it’s specific to my calls, or our account (we have the account setting for SSL on).

Topic: Highrise API / ColdFusion CFHTTP

I see an administrator post from time to time, but I don’t know if he’s an employee, or just a devotee.

Anyway, I finally found the problem. I was using “http” (which the documentation seemed to suggest using), and using “https” worked. “http” would work w/ gets, but not w/ posts.

Topic: Highrise API / Mistakes in the API documentation

Memberships (http://developer.37signals.com/highrise/memberships.shtml)

Wrong:
Destroy
GET /memberships/#{id}.xml

Right:
Destroy
DELETE /memberships/#{id}.xml

Topic: Highrise API / Mistakes in the API documentation

Groups (http://developer.37signals.com/highrise/groups.shtml)

Wrong:
Destroy
DELETE /tasks/#{id}.xml

Right:
Destroy
DELETE /groups/#{id}.xml

Topic: Highrise API / Mistakes in the API documentation

Groups (http://developer.37signals.com/highrise/groups.shtml)

Wrong Examples:
Create
<group> <name>Partners</author-id>
</group>

Update
<group> <name>Senior Partners</author-id>
</group>

Right Examples:
Create
<group> <name>Partners</name>
</group>

Update
<group> <name>Senior Partners</name>
</group>

Topic: Highrise API / Mistakes in the API documentation

Companies (http://developer.37signals.com/highrise/companies.shtml)

Wrong:
Show
GET /company/#{id}.xml

Right:
Show
GET /companies/#{id}.xml

Topic: Highrise API / Mistakes in the API documentation

Cases (http://developer.37signals.com/highrise/cases.shtml)

Wrong:
Show
GET /kase/#{id}.xml

Right:
Show
GET /kases/#{id}.xml

Topic: Highrise API / Mistakes in the API documentation

Users (http://developer.37signals.com/highrise/users.shtml)

Wrong:
Show
GET /users/#{id}.xml

Right:
Show
GET /people/#{id}.xml

Topic: Highrise API / Mistakes in the API documentation

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

After running into my third one, I’ve decided to start offering these up in the fourm as I come across them. I’m hoping they will help 37siganls to update the info, and other devs who may be suffering blood loss after beating their heads against code that can’t work ;)

Topic: Feature Requests / Add company to contact info on Dashboard/Recent History

Having the name/photo for the person there helps, but I spend a lot of time clicking through to see what company they belong to.

Maybe there could be options to choose how much detail you need on that page.

Topic: Highrise API / ColdFusion CFHTTP

Don’t think I’m going to get an answer here.

If anyone can help, I would appreciate it. Otherwise, I’ll just start talking to 37 directly. I’ll need to get answers before we can start signing up clients to use it.

Topic: Highrise API / ColdFusion CFHTTP

I have been testing more, and got a note for a case to insert fine, so my code is fine.

I think the problem is the documentation. There are a few typos, and I think there is one on the task page.

Examples of existing typos that prevent API from working:

http://developer.37signals.com/highrise/cases.shtml
To get “Show” to work, it is “GET /kases/#{id}.xml” not “GET /kase/#{id}.xml”

http://developer.37signals.com/highrise/companies.shtml
To get “Show” to work, it is “GET /companies/#{id}.xml” and not “GET /company/#{id}.xml”

I would ask 37signals to put as much polish and professionalism into their documentation as they do their products, if they plan on having serious developers use it…and take it seriously.

Can someone please audit and proof-read the documentation so we can start our programing? This is a great product, and we have a lot of plans for it, and plan to be major users.

Topic: Highrise API / ColdFusion CFHTTP

I was using this example from Basecamp (http://basecamphq.com/forum-archive/viewtopic.php?pid=8160), but it’s not working w/ Highrise. Any ideas?

Sry for the layout…I can’t get it to clean up