Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
API changes for 37signals Accounts
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Heinemeier Hansson  
View profile  
 More options Nov 30 2009, 5:05 pm
From: David Heinemeier Hansson <da...@37signals.com>
Date: Mon, 30 Nov 2009 16:05:56 -0600
Local: Mon, Nov 30 2009 5:05 pm
Subject: API changes for 37signals Accounts

Hi everyone,

We've just announced that on December 13th we'll be switching to a new authentication system for all 37signals applications: http://37signals.com/accounts

This also means that we'll be standardizing all API access to work with 37signals Accounts. We'll use a token system for all applications, similar to how we're doing it today for Backpack and Highrise.

All users will be asked to pick a new username and password and will be assigned a new API token. Once they've jumped over, they will no longer be able to access the API with their old username and password.

This is especially important for Basecamp since it didn't have an API token before. If you're developing for Basecamp, please have a look at http://developer.37signals.com/highrise/ for a preview of how the new authentication scheme will work. It basically just means using the API key as the username and nothing (or X) as the password.

Backpack and Highrise will have no changes and the old API keys will continue to work. So it should be smooth sailing.

On the same note, the HTML around account administration will change. So if you've been dipping in behind the official APIs for account and user management, these things may well break. This is especially important for Campfire which had no official API until this week's beta release.
--
David Heinemeier Hansson
37signals, Partner

  smime.p7s
3K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Doug Reeder  
View profile  
 More options Dec 7 2009, 2:50 pm
From: Doug Reeder <reeder...@gmail.com>
Date: Mon, 7 Dec 2009 14:50:37 -0500
Local: Mon, Dec 7 2009 2:50 pm
Subject: Re: [37signals API] API changes for 37signals Accounts
When will developers be able to "convert" an account to use the new  
authentication system and test their code?

Doug Reeder
reeder...@gmail.com
http://reeder29.livejournal.com/
https://twitter.com/reeder29


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
tomrossi7  
View profile  
 More options Dec 9 2009, 9:00 am
From: tomrossi7 <t...@themolehill.com>
Date: Wed, 9 Dec 2009 06:00:42 -0800 (PST)
Local: Wed, Dec 9 2009 9:00 am
Subject: Re: API changes for 37signals Accounts
The change is occurring this Saturday and I don't see how we can test
the functionality yet?  When will tokens be available for users?

Thanks,
Tom

On Dec 7, 2:50 pm, Doug Reeder <reeder...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Doug Reeder  
View profile  
 More options Dec 13 2009, 8:05 pm
From: Doug Reeder <reeder...@gmail.com>
Date: Sun, 13 Dec 2009 20:05:37 -0500
Local: Sun, Dec 13 2009 8:05 pm
Subject: Re: [37signals API] API changes for 37signals Accounts
Since customers will no longer need to remember (or bookmark) a URL to  
access Basecamp or the other apps, soon we will have many users who  
will not know what the URL of their Basecamp site is, and thus be  
unable to enter it into a 3rd party application.  Without that URL,  
3rd party apps can't use the application API.

Is there a new API, which, given a 37signals username and password,  
can return the URLs, that that account has access to?

Doug Reeder
reeder...@gmail.com
http://reeder29.livejournal.com/
https://twitter.com/reeder29


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Josh Turmel  
View profile  
 More options Dec 13 2009, 9:28 pm
From: Josh Turmel <jtur...@gmail.com>
Date: Sun, 13 Dec 2009 18:28:17 -0800 (PST)
Local: Sun, Dec 13 2009 9:28 pm
Subject: Re: API changes for 37signals Accounts
I concur, some people already have a problem figuring this out because
they bookmark the site, or for whatever reasons.

Josh

On Dec 13, 7:05 pm, Doug Reeder <reeder...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »