New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basecamp 3 API? #196

Closed
archon810 opened this Issue Nov 3, 2015 · 108 comments

Comments

Projects
None yet
@archon810

archon810 commented Nov 3, 2015

Hi,

Basecamp 3 looks great. I'd like to upgrade, but we have some integration with HipChat and BC going, and I have to make sure it works with BC3 first.

  1. Is there an API for BC3?
  2. Is there maybe existing integration planned with HipChat?

Thanks.

@jeremy

This comment has been minimized.

Show comment
Hide comment
@jeremy

jeremy Nov 3, 2015

Member

Basecamp 3 will offer a brand new API, too. Coming soon! Will keep this open until we have a link to share 😊

Member

jeremy commented Nov 3, 2015

Basecamp 3 will offer a brand new API, too. Coming soon! Will keep this open until we have a link to share 😊

@emersonveenstra

This comment has been minimized.

Show comment
Hide comment
@emersonveenstra

emersonveenstra Nov 15, 2015

Any update on this? We really want to move to BC3, but we use the API for a few custom integrations and until the API comes out, we can't switch

emersonveenstra commented Nov 15, 2015

Any update on this? We really want to move to BC3, but we use the API for a few custom integrations and until the API comes out, we can't switch

@nfm

This comment has been minimized.

Show comment
Hide comment
@nfm

nfm Nov 15, 2015

We're also interested in this at Paydirt to do our time tracking integration.

nfm commented Nov 15, 2015

We're also interested in this at Paydirt to do our time tracking integration.

@forrestolivo

This comment has been minimized.

Show comment
Hide comment
@forrestolivo

forrestolivo Nov 16, 2015

Urgently supporting this request! We have existing integrations that we'd love to use with BC3.

forrestolivo commented Nov 16, 2015

Urgently supporting this request! We have existing integrations that we'd love to use with BC3.

@emersonveenstra

This comment has been minimized.

Show comment
Hide comment
@emersonveenstra

emersonveenstra Nov 16, 2015

Doing some digging, looks like there's hidden undocumented endpoints available. Not going to say them here, but hopefully they'll polish them up soon and release it

Edit: hidden was a bad word choice. They aren't really hidden, just undocumented

emersonveenstra commented Nov 16, 2015

Doing some digging, looks like there's hidden undocumented endpoints available. Not going to say them here, but hopefully they'll polish them up soon and release it

Edit: hidden was a bad word choice. They aren't really hidden, just undocumented

@waltspence

This comment has been minimized.

Show comment
Hide comment
@smythp

This comment has been minimized.

Show comment
Hide comment
@smythp

smythp Dec 14, 2015

Any news on this? Would also like to support a request for a Basecamp 3 API.

smythp commented Dec 14, 2015

Any news on this? Would also like to support a request for a Basecamp 3 API.

@jeremy

This comment has been minimized.

Show comment
Hide comment
@jeremy

jeremy Dec 14, 2015

Member

News: We'll post here as soon as we have an early API to share with you! 😊

Member

jeremy commented Dec 14, 2015

News: We'll post here as soon as we have an early API to share with you! 😊

@smythp

This comment has been minimized.

Show comment
Hide comment
@smythp

smythp Dec 14, 2015

Great! Thank you.

On Sun, Dec 13, 2015 at 10:49 PM, Jeremy Daer notifications@github.com
wrote:

News: We'll post here as soon as we have an early API to share with you!
😊


Reply to this email directly or view it on GitHub
#196 (comment).

smythp commented Dec 14, 2015

Great! Thank you.

On Sun, Dec 13, 2015 at 10:49 PM, Jeremy Daer notifications@github.com
wrote:

News: We'll post here as soon as we have an early API to share with you!
😊


Reply to this email directly or view it on GitHub
#196 (comment).

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Dec 23, 2015

With all due respect this release schema you're following is killing your 'integration partners'. Users already have the latest and greatest Basecamp (v3) available but developers aren't able to update their integrations due to missing API documentation.

It has been a couple of months now and still not a single sign of API docs being released. Could you please provide us with a heads up on the ETA?

Some of my users state that they won't upgrade to Basecamp v3 until we're ready. That's nice of them. Others are leaving our paid plans due to lacking Basecamp v3 support. Can't blame them.

Is there anything we could do to help speed things up?

rvanbaalen commented Dec 23, 2015

With all due respect this release schema you're following is killing your 'integration partners'. Users already have the latest and greatest Basecamp (v3) available but developers aren't able to update their integrations due to missing API documentation.

It has been a couple of months now and still not a single sign of API docs being released. Could you please provide us with a heads up on the ETA?

Some of my users state that they won't upgrade to Basecamp v3 until we're ready. That's nice of them. Others are leaving our paid plans due to lacking Basecamp v3 support. Can't blame them.

Is there anything we could do to help speed things up?

@ubergeekzone

This comment has been minimized.

Show comment
Hide comment
@ubergeekzone

ubergeekzone Dec 29, 2015

What's the status of the basecamp 3 API? i love the new basecamp but it lacks a few features that i require... such as tracking git commits to bitbucket and slack chat notifications.

ubergeekzone commented Dec 29, 2015

What's the status of the basecamp 3 API? i love the new basecamp but it lacks a few features that i require... such as tracking git commits to bitbucket and slack chat notifications.

@bestwnh

This comment has been minimized.

Show comment
Hide comment
@bestwnh

bestwnh Jan 1, 2016

Hope for some status update...

bestwnh commented Jan 1, 2016

Hope for some status update...

@cnhx

This comment has been minimized.

Show comment
Hide comment
@cnhx

cnhx Jan 6, 2016

Any update on this?

cnhx commented Jan 6, 2016

Any update on this?

@t1mmen

This comment has been minimized.

Show comment
Hide comment
@t1mmen

t1mmen Jan 6, 2016

+1 to @rvanbaalen's comment. An ETA would be much appreciated.

t1mmen commented Jan 6, 2016

+1 to @rvanbaalen's comment. An ETA would be much appreciated.

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Jan 7, 2016

@jeremy When will that 'early' (late) API become available? It sounds like you don't have a v3 API at all yet?

rvanbaalen commented Jan 7, 2016

@jeremy When will that 'early' (late) API become available? It sounds like you don't have a v3 API at all yet?

@xiamx

This comment has been minimized.

Show comment
Hide comment
@xiamx

xiamx Jan 7, 2016

+1 to @rvanbaalen , it would be nice to be more transparent on this.

xiamx commented Jan 7, 2016

+1 to @rvanbaalen , it would be nice to be more transparent on this.

@samuelsimoes

This comment has been minimized.

Show comment
Hide comment
@samuelsimoes

samuelsimoes Jan 7, 2016

Also waiting it to support the new API on the Chrome Basecamp Notifier. 😞

samuelsimoes commented Jan 7, 2016

Also waiting it to support the new API on the Chrome Basecamp Notifier. 😞

@eileencodes

This comment has been minimized.

Show comment
Hide comment
@eileencodes

eileencodes Jan 8, 2016

Contributor

Hey everyone, we're definitely going to have an API but we don't have a timeline. I'm sorry that we can't give you a specific date, but know that an API is in the works. Thanks for your patience!

Contributor

eileencodes commented Jan 8, 2016

Hey everyone, we're definitely going to have an API but we don't have a timeline. I'm sorry that we can't give you a specific date, but know that an API is in the works. Thanks for your patience!

@bestwnh

This comment has been minimized.

Show comment
Hide comment
@bestwnh

bestwnh Jan 8, 2016

@eileencodes I understand. But my leader won't let me set up a todo with no due date... So at least a rough date like 3 months or something?

bestwnh commented Jan 8, 2016

@eileencodes I understand. But my leader won't let me set up a todo with no due date... So at least a rough date like 3 months or something?

@raulpopadineti

This comment has been minimized.

Show comment
Hide comment
@raulpopadineti

raulpopadineti Jan 18, 2016

+1 to @rvanbaalen. We're still waiting for the soon-to-be-released Basecamp 3 API. Still no ETA?

raulpopadineti commented Jan 18, 2016

+1 to @rvanbaalen. We're still waiting for the soon-to-be-released Basecamp 3 API. Still no ETA?

@archondigital

This comment has been minimized.

Show comment
Hide comment
@archondigital

archondigital Jan 22, 2016

Any news on the brand new API?

archondigital commented Jan 22, 2016

Any news on the brand new API?

@jeremy

This comment has been minimized.

Show comment
Hide comment
@jeremy

jeremy Jan 22, 2016

Member

Thanks for the interest, all! No fixed ETA, but it's in the works. We'll update here the moment we have news to share.

Member

jeremy commented Jan 22, 2016

Thanks for the interest, all! No fixed ETA, but it's in the works. We'll update here the moment we have news to share.

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Jan 22, 2016

With all due respect. Its nog just interest. Some of us have business critical processes linked the API that you guys decided to break with unannounced. I would have expected more developer love from Basecamp.


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 22 jan. 2016, at 16:43, Jeremy Daer notifications@github.com wrote:

Thanks for the interest, all! No fixed ETA, but it's in the works. We'll update here the moment we have news to share.


Reply to this email directly or view it on GitHub.

rvanbaalen commented Jan 22, 2016

With all due respect. Its nog just interest. Some of us have business critical processes linked the API that you guys decided to break with unannounced. I would have expected more developer love from Basecamp.


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 22 jan. 2016, at 16:43, Jeremy Daer notifications@github.com wrote:

Thanks for the interest, all! No fixed ETA, but it's in the works. We'll update here the moment we have news to share.


Reply to this email directly or view it on GitHub.

@tomdidom

This comment has been minimized.

Show comment
Hide comment

tomdidom commented Jan 22, 2016

+1 to @rvanbaalen.

@Fustrate

This comment has been minimized.

Show comment
Hide comment
@Fustrate

Fustrate Jan 22, 2016

Is there anyone actually working on the API, or is it just on a roadmap tucked away in a corner? It's been almost 3 months since v3 was released, and I hope you guys would've already been working on a public API before then.

Thanks for your patience!

There's really no patience involved when we have no other option but to wait here in the dark.

Fustrate commented Jan 22, 2016

Is there anyone actually working on the API, or is it just on a roadmap tucked away in a corner? It's been almost 3 months since v3 was released, and I hope you guys would've already been working on a public API before then.

Thanks for your patience!

There's really no patience involved when we have no other option but to wait here in the dark.

@forrestolivo

This comment has been minimized.

Show comment
Hide comment
@forrestolivo

forrestolivo Jan 22, 2016

Part of the disconnect, I think, is that this is not just normal reaction
to the Basecamp "we don't announce future stuff" thing. I can imagine being
on the Basecamp team, reading this thread, and thinking "this is just part
of being on the team of an edgy company that does stuff our own way." I
think in this case, though, in 2016, an API is not just a feature that's
nice for people to have, it's a necessary part of any product like Basecamp
at launch. If you encourage people who use your product to build things
that rely on it, you have a responsibility to them. That responsibility
goes beyond, say, the responsibility you have to people asking you to add
in whatever niche thing they want into Basecamp. I think we'd all
appreciate more detailed information, and an acknowledgment that a basic
API is uniquely not applicable to the Basecamp philosophy of "we don't
have a timeline."

On Fri, Jan 22, 2016 at 1:03 PM Steven Hoffman notifications@github.com
wrote:

Is there anyone actually working on the API, or is it just on a roadmap
tucked away in a corner? It's been almost 3 months since v3 was released,
and I hope you guys would've already been working on a public API before
then.

Thanks for your patience!

There's really no patience involved when we have no other option but to
wait here in the dark.


Reply to this email directly or view it on GitHub
#196 (comment).

forrestolivo commented Jan 22, 2016

Part of the disconnect, I think, is that this is not just normal reaction
to the Basecamp "we don't announce future stuff" thing. I can imagine being
on the Basecamp team, reading this thread, and thinking "this is just part
of being on the team of an edgy company that does stuff our own way." I
think in this case, though, in 2016, an API is not just a feature that's
nice for people to have, it's a necessary part of any product like Basecamp
at launch. If you encourage people who use your product to build things
that rely on it, you have a responsibility to them. That responsibility
goes beyond, say, the responsibility you have to people asking you to add
in whatever niche thing they want into Basecamp. I think we'd all
appreciate more detailed information, and an acknowledgment that a basic
API is uniquely not applicable to the Basecamp philosophy of "we don't
have a timeline."

On Fri, Jan 22, 2016 at 1:03 PM Steven Hoffman notifications@github.com
wrote:

Is there anyone actually working on the API, or is it just on a roadmap
tucked away in a corner? It's been almost 3 months since v3 was released,
and I hope you guys would've already been working on a public API before
then.

Thanks for your patience!

There's really no patience involved when we have no other option but to
wait here in the dark.


Reply to this email directly or view it on GitHub
#196 (comment).

@jeremy

This comment has been minimized.

Show comment
Hide comment
@jeremy

jeremy Jan 22, 2016

Member

I hear you! And totally agree. We'll discuss how to open up our progress to you sooner than later.

Basecamp 3 is designed with API integration in mind from the get-go. We're proving that out with our mobile apps.

Those of you blocked on API availability: please email me to share how'd you aim to integrate with Basecamp 3. It'll help guide our choices for the initial API release.

Member

jeremy commented Jan 22, 2016

I hear you! And totally agree. We'll discuss how to open up our progress to you sooner than later.

Basecamp 3 is designed with API integration in mind from the get-go. We're proving that out with our mobile apps.

Those of you blocked on API availability: please email me to share how'd you aim to integrate with Basecamp 3. It'll help guide our choices for the initial API release.

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Jan 22, 2016

Lets not close up again and learn from earlier comments in this thread Jeremy. Why not discuss these things publicly here, on Github?

Regarding your question on how I would aim to integrate with Basecamp 3: take a look at the long list of applications that are compatible with Basecamp 2. How about making the basic v2 API compatible with v3? As in; getting a list of Basecamps os nothing new right? Or at least providing a way for developers to differentiate on Basecamp Classic (basecamp), Basecamp v2 (bcx) and Basecamp 3 (bc3?) accounts would be helpful. That way our applications wont have to randomly crash because a v3 user tries to connect on a v2 API. Right now, v3 users have the v2 identifier 'bcx' which is VERY unwanted.

That could at least be a quick fix for us developers to provide decent feedback "Sorry Basecamp v3 isn't compatible with anything yet." to our users.


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 22 jan. 2016, at 17:27, Jeremy Daer notifications@github.com wrote:

I hear you! And totally agree. We'll discuss how to open up our progress to you sooner than later.

Basecamp 3 is designed with API integration in mind from the get-go. We're proving that out with our mobile apps.

Those of you blocked on API availability: please email me to share how'd you aim to integrate with Basecamp 3. It'll help guide our choices for the initial API release.


Reply to this email directly or view it on GitHub.

rvanbaalen commented Jan 22, 2016

Lets not close up again and learn from earlier comments in this thread Jeremy. Why not discuss these things publicly here, on Github?

Regarding your question on how I would aim to integrate with Basecamp 3: take a look at the long list of applications that are compatible with Basecamp 2. How about making the basic v2 API compatible with v3? As in; getting a list of Basecamps os nothing new right? Or at least providing a way for developers to differentiate on Basecamp Classic (basecamp), Basecamp v2 (bcx) and Basecamp 3 (bc3?) accounts would be helpful. That way our applications wont have to randomly crash because a v3 user tries to connect on a v2 API. Right now, v3 users have the v2 identifier 'bcx' which is VERY unwanted.

That could at least be a quick fix for us developers to provide decent feedback "Sorry Basecamp v3 isn't compatible with anything yet." to our users.


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 22 jan. 2016, at 17:27, Jeremy Daer notifications@github.com wrote:

I hear you! And totally agree. We'll discuss how to open up our progress to you sooner than later.

Basecamp 3 is designed with API integration in mind from the get-go. We're proving that out with our mobile apps.

Those of you blocked on API availability: please email me to share how'd you aim to integrate with Basecamp 3. It'll help guide our choices for the initial API release.


Reply to this email directly or view it on GitHub.

@kennebel

This comment has been minimized.

Show comment
Hide comment
@kennebel

kennebel Jan 22, 2016

The company I work for is also stuck. We have multiple processes that rely on third-party and internal integration. We cannot abandon our work flow with no hint of when automated integration will return.

I am fairly concerned with the idea that 2 hours ago, it was suggested that this is a great time to provide input on the direction of the API. Several months after release of the product, the API should only be delayed for bug testing, "guide our choices" should be so far in the rear-view mirror, that you can't pick it out anymore.

:(

kennebel commented Jan 22, 2016

The company I work for is also stuck. We have multiple processes that rely on third-party and internal integration. We cannot abandon our work flow with no hint of when automated integration will return.

I am fairly concerned with the idea that 2 hours ago, it was suggested that this is a great time to provide input on the direction of the API. Several months after release of the product, the API should only be delayed for bug testing, "guide our choices" should be so far in the rear-view mirror, that you can't pick it out anymore.

:(

@jeremy

This comment has been minimized.

Show comment
Hide comment
@jeremy

jeremy Jan 23, 2016

Member

Right now, v3 users have the v2 identifier 'bcx' which is VERY unwanted.

Definitely shouldn't be seeing this, @rvanbaalen. Send an email to support@basecamp.com and we'll troubleshoot with you. (I'm happy to discuss here, too.)

Member

jeremy commented Jan 23, 2016

Right now, v3 users have the v2 identifier 'bcx' which is VERY unwanted.

Definitely shouldn't be seeing this, @rvanbaalen. Send an email to support@basecamp.com and we'll troubleshoot with you. (I'm happy to discuss here, too.)

@jeremy

This comment has been minimized.

Show comment
Hide comment
@jeremy

jeremy Jan 23, 2016

Member

@rvanbaalen, @kennebel, and all – I ask for feedback because I know you're sitting on your hands, waiting for release, feeling between a rock & hard place with your own customers and teams who depend on you. I'm here to help. Your feedback can clarify our release priorities: what to expose first vs. what may come later. Squints in the rear-view mirror. 😯

@kennebel, I'd love to hear about the workflow you've built with 3rd-party and in-house integrations. Up for sharing?

Member

jeremy commented Jan 23, 2016

@rvanbaalen, @kennebel, and all – I ask for feedback because I know you're sitting on your hands, waiting for release, feeling between a rock & hard place with your own customers and teams who depend on you. I'm here to help. Your feedback can clarify our release priorities: what to expose first vs. what may come later. Squints in the rear-view mirror. 😯

@kennebel, I'd love to hear about the workflow you've built with 3rd-party and in-house integrations. Up for sharing?

@ubergeekzone

This comment has been minimized.

Show comment
Hide comment
@ubergeekzone

ubergeekzone Jan 23, 2016

@jeremy I tried to reach you guy's through twitter about offering a helping hand with development to speed up your API. Shoot me an email at amy.bridges@invoate.com and we can chat a little more there about lending a helping hand.

ubergeekzone commented Jan 23, 2016

@jeremy I tried to reach you guy's through twitter about offering a helping hand with development to speed up your API. Shoot me an email at amy.bridges@invoate.com and we can chat a little more there about lending a helping hand.

@kennebel

This comment has been minimized.

Show comment
Hide comment
@kennebel

kennebel Jan 26, 2016

@jeremy We take all of the useful date information from basecamp, the budgeted hours from another service that tracks time budgets and per task time spent, and build a continuously updated chart that shows the next several months of anticipated work load. Helps with scheduling people, contractor resources, and the like. Rather than guessing "how busy" a team is, I can point at a column chart, and tell them exactly when they'll be working over time, and when they should take a day off. :)

kennebel commented Jan 26, 2016

@jeremy We take all of the useful date information from basecamp, the budgeted hours from another service that tracks time budgets and per task time spent, and build a continuously updated chart that shows the next several months of anticipated work load. Helps with scheduling people, contractor resources, and the like. Rather than guessing "how busy" a team is, I can point at a column chart, and tell them exactly when they'll be working over time, and when they should take a day off. :)

@cbaci

This comment has been minimized.

Show comment
Hide comment
@cbaci

cbaci Jan 29, 2016

Oh .... I've got a dashboard inside me that wants to come out .... #musthaveapi ... please BC3 dev ... before it's too late ... #agencyprincipalsneedprettycharts

cbaci commented Jan 29, 2016

Oh .... I've got a dashboard inside me that wants to come out .... #musthaveapi ... please BC3 dev ... before it's too late ... #agencyprincipalsneedprettycharts

@acurley

This comment has been minimized.

Show comment
Hide comment
@acurley

acurley Jan 31, 2016

I'm super disappointed in Basecamp here. I recommended this product to my wife and her company just assuming that Basecamp would have an API with which she could integrate. I cannot believe that the company I believed to be one of the great homes of RoR and @dhh would neglect to put API integrations first and foremost in their development cycle.

acurley commented Jan 31, 2016

I'm super disappointed in Basecamp here. I recommended this product to my wife and her company just assuming that Basecamp would have an API with which she could integrate. I cannot believe that the company I believed to be one of the great homes of RoR and @dhh would neglect to put API integrations first and foremost in their development cycle.

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Jan 31, 2016

Member

We will get an API out. But we've had other, more important things higher
on the todo list after launch. If having an API available right now is the
most important thing about Basecamp for you, you can also give Basecamp 2 a
shot. Still a great product. If not, hopefully it won't be too much longer
before we have the API ready.

On Sun, Jan 31, 2016 at 5:46 PM, Andrew Curley notifications@github.com
wrote:

I'm super disappointed in Basecamp here. I recommended this product to my
wife and her company just assuming that Basecamp would have an API with
which she could integrate I cannot believe that the company I believed to
be one of the great homes of RoR and @dhh https://github.com/dhh would
neglect to put API integrations first and foremost in their development
cycle.


Reply to this email directly or view it on GitHub
#196 (comment).

Member

dhh commented Jan 31, 2016

We will get an API out. But we've had other, more important things higher
on the todo list after launch. If having an API available right now is the
most important thing about Basecamp for you, you can also give Basecamp 2 a
shot. Still a great product. If not, hopefully it won't be too much longer
before we have the API ready.

On Sun, Jan 31, 2016 at 5:46 PM, Andrew Curley notifications@github.com
wrote:

I'm super disappointed in Basecamp here. I recommended this product to my
wife and her company just assuming that Basecamp would have an API with
which she could integrate I cannot believe that the company I believed to
be one of the great homes of RoR and @dhh https://github.com/dhh would
neglect to put API integrations first and foremost in their development
cycle.


Reply to this email directly or view it on GitHub
#196 (comment).

@troy

This comment has been minimized.

Show comment
Hide comment
@troy

troy Jan 31, 2016

@jeremy in answer to your last comment, the API target I'd use is "all incomplete todos I'm assigned" or if it's materially easier, "all incomplete todos I have access to." https://twitter.com/tacoapp/status/692520150088704001 has more.

troy commented Jan 31, 2016

@jeremy in answer to your last comment, the API target I'd use is "all incomplete todos I'm assigned" or if it's materially easier, "all incomplete todos I have access to." https://twitter.com/tacoapp/status/692520150088704001 has more.

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Jan 31, 2016

@dhh With all due respect have you read the replies in this topic?

Most of us aren't 'fiddling around with the Basecamp API'. We're all businesses who have hundreds (thousands) of users that rely on the connectivity between our apps and Basecamp.

It's not up to us to choose which version our users pick. We have real-world users who are being pushed (marketed) by Basecamp to upgrade their accounts to the latest Basecamp (v3). That's all very understandable. The problem here relies in the fact that yet again a Basecamp employee confirms that there are 'more important things' than delivering an API in time, months after the Basecamp 3 release.

FYI; This topic started 5 november. The issue we're discussing here started the moment Basecamp 3 was live. For a company as big as Basecamp, I would expect that developing, testing and releasing an API with a new software release would take less than three months to accomplish.

Regarding the prioritizing of Basecamp API features @jeremy asked about; please just make the v2 API compatible with v3 without adding whatever fancy new stuff you're planning so we can at least get things working the way they were working before and make our customers happy again.

rvanbaalen commented Jan 31, 2016

@dhh With all due respect have you read the replies in this topic?

Most of us aren't 'fiddling around with the Basecamp API'. We're all businesses who have hundreds (thousands) of users that rely on the connectivity between our apps and Basecamp.

It's not up to us to choose which version our users pick. We have real-world users who are being pushed (marketed) by Basecamp to upgrade their accounts to the latest Basecamp (v3). That's all very understandable. The problem here relies in the fact that yet again a Basecamp employee confirms that there are 'more important things' than delivering an API in time, months after the Basecamp 3 release.

FYI; This topic started 5 november. The issue we're discussing here started the moment Basecamp 3 was live. For a company as big as Basecamp, I would expect that developing, testing and releasing an API with a new software release would take less than three months to accomplish.

Regarding the prioritizing of Basecamp API features @jeremy asked about; please just make the v2 API compatible with v3 without adding whatever fancy new stuff you're planning so we can at least get things working the way they were working before and make our customers happy again.

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Feb 26, 2016

Member

The work is underway. That's all I can say at this point. @qrush will
follow up with the specific progress when he has something to share.

On Fri, Feb 26, 2016 at 2:40 PM, Raul Popadineti notifications@github.com
wrote:

@dhh https://github.com/dhh how soon is "very shortly"?

And thank you for keeping us up-to-date with the process.


Reply to this email directly or view it on GitHub
#196 (comment).

Member

dhh commented Feb 26, 2016

The work is underway. That's all I can say at this point. @qrush will
follow up with the specific progress when he has something to share.

On Fri, Feb 26, 2016 at 2:40 PM, Raul Popadineti notifications@github.com
wrote:

@dhh https://github.com/dhh how soon is "very shortly"?

And thank you for keeping us up-to-date with the process.


Reply to this email directly or view it on GitHub
#196 (comment).

@cbaci

This comment has been minimized.

Show comment
Hide comment
@cbaci

cbaci Feb 29, 2016

@qrush, perhaps you can give a quick hint on the authentication mechanism you'll be using, Oauth2?

cbaci commented Feb 29, 2016

@qrush, perhaps you can give a quick hint on the authentication mechanism you'll be using, Oauth2?

@qrush

This comment has been minimized.

Show comment
Hide comment
@qrush

qrush Feb 29, 2016

Contributor

@cbaci Yep, it'll be OAuth2 just like the BC2 API. More on our authentication scheme is here: https://github.com/basecamp/api/blob/master/sections/authentication.md

Contributor

qrush commented Feb 29, 2016

@cbaci Yep, it'll be OAuth2 just like the BC2 API. More on our authentication scheme is here: https://github.com/basecamp/api/blob/master/sections/authentication.md

@u-clarkdeveloper

This comment has been minimized.

Show comment
Hide comment
@u-clarkdeveloper

u-clarkdeveloper Feb 29, 2016

Looking forward to V3.

u-clarkdeveloper commented Feb 29, 2016

Looking forward to V3.

@cbaci

This comment has been minimized.

Show comment
Hide comment
@cbaci

cbaci commented Feb 29, 2016

TY @qrush

@kennebel

This comment has been minimized.

Show comment
Hide comment
@kennebel

kennebel Mar 7, 2016

Out of curiosity, will the new API be designed "corporate programmer friendly"? By this I mean, I am a corporate programmer, I am NOT on every project/basecamp in the company. However, when mgmt wants a report, they want all projects included (some of which they may not be included on, because there wasn't a reason to).

At this time, that means that I have to store the username/password of a couple of different users in order to gain access to all projects. (i don't feel good about storing the "owner" account info in a piece of code, just like I would never use Windows "Administrator" in code)

I'd like to see in the API, an option that if the account I'm using is an administrative one, it can see everything. Certainly, if the credentials used are not in the administrator group limit the view.

Thoughts?

kennebel commented Mar 7, 2016

Out of curiosity, will the new API be designed "corporate programmer friendly"? By this I mean, I am a corporate programmer, I am NOT on every project/basecamp in the company. However, when mgmt wants a report, they want all projects included (some of which they may not be included on, because there wasn't a reason to).

At this time, that means that I have to store the username/password of a couple of different users in order to gain access to all projects. (i don't feel good about storing the "owner" account info in a piece of code, just like I would never use Windows "Administrator" in code)

I'd like to see in the API, an option that if the account I'm using is an administrative one, it can see everything. Certainly, if the credentials used are not in the administrator group limit the view.

Thoughts?

@qrush

This comment has been minimized.

Show comment
Hide comment
@qrush

qrush Mar 17, 2016

Contributor

@kennebel good question! You'd probably want to store the OAuth tokens that an owner signed in with and not their username/password. Just like you'd do for implementing with any other service - you wouldn't store someone's Twitter password (or even ask for it) - you'd go through their authentication flow and store the access tokens after.

Contributor

qrush commented Mar 17, 2016

@kennebel good question! You'd probably want to store the OAuth tokens that an owner signed in with and not their username/password. Just like you'd do for implementing with any other service - you wouldn't store someone's Twitter password (or even ask for it) - you'd go through their authentication flow and store the access tokens after.

@EMIjess

This comment has been minimized.

Show comment
Hide comment
@EMIjess

EMIjess Mar 18, 2016

Is it crazy to still be interested in the timeline on which we can expect a public API for basecamp3?

EMIjess commented Mar 18, 2016

Is it crazy to still be interested in the timeline on which we can expect a public API for basecamp3?

@stevish-com

This comment has been minimized.

Show comment
Hide comment
@stevish-com

stevish-com Mar 18, 2016

@EMIjess I feel that way too. It's all I can do not to come on here every day and say "Is it done yet, is it done yet?" I have a few tasks on my docket that are only waiting on the Basecamp3 API release, and I'm itching to get started on them (client is more patient than I am!)

stevish-com commented Mar 18, 2016

@EMIjess I feel that way too. It's all I can do not to come on here every day and say "Is it done yet, is it done yet?" I have a few tasks on my docket that are only waiting on the Basecamp3 API release, and I'm itching to get started on them (client is more patient than I am!)

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Mar 18, 2016

So many basecamp users are still so unaware about the fact that no third party is able to work with Basecamp 3 (yet..). I think Basecamp could do a better job informing their users about this. Perhaps even a blogpost or something.

November 2015 was the date Basecamp 3 was released if Im correct. In internet tech terms thats almost a decade ago and still no ETA for the API.


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 17 mrt. 2016, at 21:19, Stephen Narwold notifications@github.com wrote:

@EMIjess I feel that way too. It's all I can do not to come on here every day and say "Is it done yet, is it done yet?" I have a few tasks on my docket that are only waiting on the Basecamp3 API release, and I'm itching to get started on them (client is more patient than I am!)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

rvanbaalen commented Mar 18, 2016

So many basecamp users are still so unaware about the fact that no third party is able to work with Basecamp 3 (yet..). I think Basecamp could do a better job informing their users about this. Perhaps even a blogpost or something.

November 2015 was the date Basecamp 3 was released if Im correct. In internet tech terms thats almost a decade ago and still no ETA for the API.


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 17 mrt. 2016, at 21:19, Stephen Narwold notifications@github.com wrote:

@EMIjess I feel that way too. It's all I can do not to come on here every day and say "Is it done yet, is it done yet?" I have a few tasks on my docket that are only waiting on the Basecamp3 API release, and I'm itching to get started on them (client is more patient than I am!)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@qrush

This comment has been minimized.

Show comment
Hide comment
@qrush

qrush Mar 18, 2016

Contributor

Hi everyone. I'd appreciate a few minutes of your time.

Sorry.

We could have done a better job of setting expectations about our API and calming the doubts in this thread. For that I apologize on behalf of Basecamp and our team of developers, designers, and more. We rely on our development community to bring great things into (and out of) Basecamp, and it shows. Thanks for your patience and bearing with us as we've launched a new version of our product.

Let's get started.

I'd like to announce that we're starting an early access program that will let you get into our API now, with a few notes:

  1. We have a small subset of API endpoints ready for use, with a roadmap for what's next on deck
  2. This is purely for those wanting to line up their integrations for launch once the API is public + give us feedback on how it's working
  3. We don't have a specific release date yet for public launch

To apply for this early access program, just leave a 👍 reaction on this comment and I'll add you to our Basecamp 3 API documentation repo fill out this form: https://basecamp.wufoo.com/forms/request-early-access-to-the-basecamp-3-api/ (Please don't leave a real comment and spam the thread more for access!)

🚂 🙇

Contributor

qrush commented Mar 18, 2016

Hi everyone. I'd appreciate a few minutes of your time.

Sorry.

We could have done a better job of setting expectations about our API and calming the doubts in this thread. For that I apologize on behalf of Basecamp and our team of developers, designers, and more. We rely on our development community to bring great things into (and out of) Basecamp, and it shows. Thanks for your patience and bearing with us as we've launched a new version of our product.

Let's get started.

I'd like to announce that we're starting an early access program that will let you get into our API now, with a few notes:

  1. We have a small subset of API endpoints ready for use, with a roadmap for what's next on deck
  2. This is purely for those wanting to line up their integrations for launch once the API is public + give us feedback on how it's working
  3. We don't have a specific release date yet for public launch

To apply for this early access program, just leave a 👍 reaction on this comment and I'll add you to our Basecamp 3 API documentation repo fill out this form: https://basecamp.wufoo.com/forms/request-early-access-to-the-basecamp-3-api/ (Please don't leave a real comment and spam the thread more for access!)

🚂 🙇

@muesliq

This comment has been minimized.

Show comment
Hide comment
@muesliq

muesliq Apr 2, 2016

Will the new API enable us to migrate users from BC1 and BC2 to BC3 in a way that they keep their accounts? Or are we stuck with legacy products "until the end of the internet"?

muesliq commented Apr 2, 2016

Will the new API enable us to migrate users from BC1 and BC2 to BC3 in a way that they keep their accounts? Or are we stuck with legacy products "until the end of the internet"?

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Apr 4, 2016

Member

Helge,

Not sure I understand the question. But you will be able to create and read
content from BC3 using the API. You can use this in combination with the
APIs for Basecamp Classic and Basecamp 2 to copy data between the different
versions. And yes, you're welcome to use any version of Basecamp until the
end of the internet.

On Sat, Apr 2, 2016 at 10:16 AM, Helge Fahrnberger <notifications@github.com

wrote:

Will the new API enable us to migrate users from BC1 and BC2 to BC3 in a
way that they keep their accounts? Or are we stuck with legacy products
"until the end of the internet"?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

Member

dhh commented Apr 4, 2016

Helge,

Not sure I understand the question. But you will be able to create and read
content from BC3 using the API. You can use this in combination with the
APIs for Basecamp Classic and Basecamp 2 to copy data between the different
versions. And yes, you're welcome to use any version of Basecamp until the
end of the internet.

On Sat, Apr 2, 2016 at 10:16 AM, Helge Fahrnberger <notifications@github.com

wrote:

Will the new API enable us to migrate users from BC1 and BC2 to BC3 in a
way that they keep their accounts? Or are we stuck with legacy products
"until the end of the internet"?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

@muesliq

This comment has been minimized.

Show comment
Hide comment
@muesliq

muesliq Apr 4, 2016

David, I'm trying to find out beyond doubt if I will be able to use the API to migrate content and users from BC1 to BC3, in a way that (my customers') existing user accounts continue to work.

(As - for some mysterious reason - you provide no migration logic from previous versions to 3.)

muesliq commented Apr 4, 2016

David, I'm trying to find out beyond doubt if I will be able to use the API to migrate content and users from BC1 to BC3, in a way that (my customers') existing user accounts continue to work.

(As - for some mysterious reason - you provide no migration logic from previous versions to 3.)

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Apr 4, 2016

Member

Helge, it's not likely that we will offer an API for creating users as
these requests would require knowledge of someone's password. Basecamp
users all have a Basecamp ID that can give them access to any number of
accounts.

We are, however, going to investigate an official migration path later this
year.

On Mon, Apr 4, 2016 at 10:09 AM, Helge Fahrnberger <notifications@github.com

wrote:

David, I'm trying to find out beyond doubt if I will be able to use the
API to migrate content and users from BC1 to BC3, in a way that (my
customers') existing user accounts continue to work.

(As - for some misterious reason - you provide no migration logic between
from previous versions to 3.)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

Member

dhh commented Apr 4, 2016

Helge, it's not likely that we will offer an API for creating users as
these requests would require knowledge of someone's password. Basecamp
users all have a Basecamp ID that can give them access to any number of
accounts.

We are, however, going to investigate an official migration path later this
year.

On Mon, Apr 4, 2016 at 10:09 AM, Helge Fahrnberger <notifications@github.com

wrote:

David, I'm trying to find out beyond doubt if I will be able to use the
API to migrate content and users from BC1 to BC3, in a way that (my
customers') existing user accounts continue to work.

(As - for some misterious reason - you provide no migration logic between
from previous versions to 3.)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

@muesliq

This comment has been minimized.

Show comment
Hide comment
@muesliq

muesliq Apr 4, 2016

David, I'm not asking to create new users if that was unclear. I of course just want to transfer user references from BC1 projects to BC3 projects.

Or put differently:

Will I be able to able to use the API to write my own migration if I don't want to wait until "later this year", let alone submit myself to the outcome of that "investigation"?

muesliq commented Apr 4, 2016

David, I'm not asking to create new users if that was unclear. I of course just want to transfer user references from BC1 projects to BC3 projects.

Or put differently:

Will I be able to able to use the API to write my own migration if I don't want to wait until "later this year", let alone submit myself to the outcome of that "investigation"?

@stevish-com

This comment has been minimized.

Show comment
Hide comment
@stevish-com

stevish-com Apr 4, 2016

I think there's no need to "migrate" users since a basecamp 1 user can
simply be added to a basecamp in basecamp 3. All the basecamp use the same
users as far as I can tell. In my menu, I see one v1 basecamp I have access
to, one v2 basecamp, and 2 v3 basecamp and can easily switch between them.

-Stephen
On Apr 4, 2016 4:37 AM, "Helge Fahrnberger" notifications@github.com
wrote:

David, I'm not asking to create new users if that was unclear. I of course
just want to transfer user references from BC1 projects to BC3 projects.

Or put differently:

Will I be able to able to use the API to write my own migration if I don't
want to wait until "later this year", let alone submit myself to the
outcome of that "investigation"?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#196 (comment)

stevish-com commented Apr 4, 2016

I think there's no need to "migrate" users since a basecamp 1 user can
simply be added to a basecamp in basecamp 3. All the basecamp use the same
users as far as I can tell. In my menu, I see one v1 basecamp I have access
to, one v2 basecamp, and 2 v3 basecamp and can easily switch between them.

-Stephen
On Apr 4, 2016 4:37 AM, "Helge Fahrnberger" notifications@github.com
wrote:

David, I'm not asking to create new users if that was unclear. I of course
just want to transfer user references from BC1 projects to BC3 projects.

Or put differently:

Will I be able to able to use the API to write my own migration if I don't
want to wait until "later this year", let alone submit myself to the
outcome of that "investigation"?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#196 (comment)

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Apr 4, 2016

Member

Basecamp shares identities between all versions, but while there's only one
identity for many accounts, there's still one user for each account.

Helge, we'll need to think more about how to support that use case. As it
stands now, the API is authenticated for one user. That user cannot
impersonate/post as someone else on the account. If it could, I could use
my API authentication to post as Jason Fried. I don't think he would like
that :D,

If you got each of the users you want to migrate to authenticate via your
system, though, that should work. Basically, building a migrator per-user,
per-Basecamp. That'd be cool.

On Mon, Apr 4, 2016 at 12:50 PM, Stephen Narwold notifications@github.com
wrote:

I think there's no need to "migrate" users since a basecamp 1 user can
simply be added to a basecamp in basecamp 3. All the basecamp use the same
users as far as I can tell. In my menu, I see one v1 basecamp I have access
to, one v2 basecamp, and 2 v3 basecamp and can easily switch between them.

-Stephen
On Apr 4, 2016 4:37 AM, "Helge Fahrnberger" notifications@github.com
wrote:

David, I'm not asking to create new users if that was unclear. I of
course
just want to transfer user references from BC1 projects to BC3 projects.

Or put differently:

Will I be able to able to use the API to write my own migration if I
don't
want to wait until "later this year", let alone submit myself to the
outcome of that "investigation"?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#196 (comment)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

Member

dhh commented Apr 4, 2016

Basecamp shares identities between all versions, but while there's only one
identity for many accounts, there's still one user for each account.

Helge, we'll need to think more about how to support that use case. As it
stands now, the API is authenticated for one user. That user cannot
impersonate/post as someone else on the account. If it could, I could use
my API authentication to post as Jason Fried. I don't think he would like
that :D,

If you got each of the users you want to migrate to authenticate via your
system, though, that should work. Basically, building a migrator per-user,
per-Basecamp. That'd be cool.

On Mon, Apr 4, 2016 at 12:50 PM, Stephen Narwold notifications@github.com
wrote:

I think there's no need to "migrate" users since a basecamp 1 user can
simply be added to a basecamp in basecamp 3. All the basecamp use the same
users as far as I can tell. In my menu, I see one v1 basecamp I have access
to, one v2 basecamp, and 2 v3 basecamp and can easily switch between them.

-Stephen
On Apr 4, 2016 4:37 AM, "Helge Fahrnberger" notifications@github.com
wrote:

David, I'm not asking to create new users if that was unclear. I of
course
just want to transfer user references from BC1 projects to BC3 projects.

Or put differently:

Will I be able to able to use the API to write my own migration if I
don't
want to wait until "later this year", let alone submit myself to the
outcome of that "investigation"?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#196 (comment)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

@muesliq

This comment has been minimized.

Show comment
Hide comment
@muesliq

muesliq Apr 4, 2016

So I am stuck in Basecamp Classic until maybe (!) some time (!) there will be a migration routine. I'm close to migrating to Teamwork.com, despite having to make all those customer users sign up there again.. frustrated

muesliq commented Apr 4, 2016

So I am stuck in Basecamp Classic until maybe (!) some time (!) there will be a migration routine. I'm close to migrating to Teamwork.com, despite having to make all those customer users sign up there again.. frustrated

@dhh

This comment has been minimized.

Show comment
Hide comment
@dhh

dhh Apr 4, 2016

Member

Helge, sorry for the frustration. I wish I could wave a magic wand and have
all the features I'd like for Basecamp done yesterday. We'd surely have
bullet-proof migration from all previous versions of Basecamp! We've made a
commitment to exploring migration in the first half of this year, and we
will surely do that.

In the mean time, I can recommend using Basecamp 3 for brand new projects
and Basecamps and leave data for previous projects in the version of
Basecamp you had them. That's what we're doing at Basecamp ourselves. We
have data in all three versions of Basecamp. They're linked through the
account menu, so it's just a click away to jump between them.

That way you also don't disrupt any in-flight projects. We found that to be
helpful at Basecamp at with most customers we've talked to.

Fully understand the desire of "hey, we just want it all in one place". But
this is where we are at the moment.

On Mon, Apr 4, 2016 at 2:19 PM, Helge Fahrnberger notifications@github.com
wrote:

So I am stuck in Basecamp Classic until maybe (!) some time (!) there will
be a migration routine. I'm close to migrate to Teamwork.com, despite
having to make all those customer users sign up there again.. frustrated


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

Member

dhh commented Apr 4, 2016

Helge, sorry for the frustration. I wish I could wave a magic wand and have
all the features I'd like for Basecamp done yesterday. We'd surely have
bullet-proof migration from all previous versions of Basecamp! We've made a
commitment to exploring migration in the first half of this year, and we
will surely do that.

In the mean time, I can recommend using Basecamp 3 for brand new projects
and Basecamps and leave data for previous projects in the version of
Basecamp you had them. That's what we're doing at Basecamp ourselves. We
have data in all three versions of Basecamp. They're linked through the
account menu, so it's just a click away to jump between them.

That way you also don't disrupt any in-flight projects. We found that to be
helpful at Basecamp at with most customers we've talked to.

Fully understand the desire of "hey, we just want it all in one place". But
this is where we are at the moment.

On Mon, Apr 4, 2016 at 2:19 PM, Helge Fahrnberger notifications@github.com
wrote:

So I am stuck in Basecamp Classic until maybe (!) some time (!) there will
be a migration routine. I'm close to migrate to Teamwork.com, despite
having to make all those customer users sign up there again.. frustrated


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#196 (comment)

@misterzik

This comment has been minimized.

Show comment
Hide comment
@misterzik

misterzik Apr 4, 2016

@qrush hey I would like access to the beta, if it's still open nickjrod at gmail.com

Thanks Nick,

  • Nick

misterzik commented Apr 4, 2016

@qrush hey I would like access to the beta, if it's still open nickjrod at gmail.com

Thanks Nick,

  • Nick
@michaeldtodd

This comment has been minimized.

Show comment
Hide comment
@michaeldtodd

michaeldtodd Apr 15, 2016

Where exactly can we change between basecamp versions? I don't see any menu that has it listed...

michaeldtodd commented Apr 15, 2016

Where exactly can we change between basecamp versions? I don't see any menu that has it listed...

@ivanbozic

This comment has been minimized.

Show comment
Hide comment
@ivanbozic

ivanbozic Apr 15, 2016

@michaeldtodd, in Basecamp 2 there should be a persistent black bar at the top of the screen where you can switch between versions.

In Basecamp 3, if you click on the Basecamp icon in the top left-hand corner, there should be a Switch Accounts area where you can do the same thing.

ivanbozic commented Apr 15, 2016

@michaeldtodd, in Basecamp 2 there should be a persistent black bar at the top of the screen where you can switch between versions.

In Basecamp 3, if you click on the Basecamp icon in the top left-hand corner, there should be a Switch Accounts area where you can do the same thing.

@joehanchoi

This comment has been minimized.

Show comment
Hide comment
@joehanchoi

joehanchoi May 17, 2016

Any ETA on these APIs going public yet?

joehanchoi commented May 17, 2016

Any ETA on these APIs going public yet?

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen May 17, 2016

Would love to know an ETA as well since our integration is receiving more and more Basecamp 3 users (who converted from Basecamp 2) and keep asking us why our tool wont work.

Right now all I can give them is "Ask Basecamp". I would love to be able to answer something along the lines of "Be patient one more week/month and we will offer BC3 support."


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 17 mei 2016, at 10:54, Joe Choi notifications@github.com wrote:

Any ETA on these APIs going public yet?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

rvanbaalen commented May 17, 2016

Would love to know an ETA as well since our integration is receiving more and more Basecamp 3 users (who converted from Basecamp 2) and keep asking us why our tool wont work.

Right now all I can give them is "Ask Basecamp". I would love to be able to answer something along the lines of "Be patient one more week/month and we will offer BC3 support."


This email was sent from my iPhone and therefore subject to typos and other inaccuracies.

On 17 mei 2016, at 10:54, Joe Choi notifications@github.com wrote:

Any ETA on these APIs going public yet?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@javan

This comment has been minimized.

Show comment
Hide comment
@javan

javan May 17, 2016

Member

Quick update: We hit a few speed bumps along the way, but work on the BC3 API is progressing and we hope to release it publicly soon. We don't have an exact ETA, and I apologize for the delays.

You can request early access to the API by filling out this form: https://basecamp.wufoo.com/forms/request-early-access-to-the-basecamp-3-api/

Member

javan commented May 17, 2016

Quick update: We hit a few speed bumps along the way, but work on the BC3 API is progressing and we hope to release it publicly soon. We don't have an exact ETA, and I apologize for the delays.

You can request early access to the API by filling out this form: https://basecamp.wufoo.com/forms/request-early-access-to-the-basecamp-3-api/

@keni-m-patel

This comment has been minimized.

Show comment
Hide comment
@keni-m-patel

keni-m-patel May 18, 2016

We've requested early access but haven't gotten any response. For me this is a business critical issue and would like to be able to eliminate some of the manual processes that are in place in our organization due to our transition from BC2 to BC3.

keni-m-patel commented May 18, 2016

We've requested early access but haven't gotten any response. For me this is a business critical issue and would like to be able to eliminate some of the manual processes that are in place in our organization due to our transition from BC2 to BC3.

@bcjarrett

This comment has been minimized.

Show comment
Hide comment
@bcjarrett

bcjarrett Jun 6, 2016

@qrush was doing a great, transparent job, but since he stopped posting there's been no update since mid-april. I know you don't want to give us an ETA, but an order of magnitude would be fantastic. Are we looking at days, weeks, months, sometime this year?

We've been working with a partially functional api for months now, and it'd be great to tell my internal customers something other than, 'I have no idea if or when I'll be able to implement that for you'.

bcjarrett commented Jun 6, 2016

@qrush was doing a great, transparent job, but since he stopped posting there's been no update since mid-april. I know you don't want to give us an ETA, but an order of magnitude would be fantastic. Are we looking at days, weeks, months, sometime this year?

We've been working with a partially functional api for months now, and it'd be great to tell my internal customers something other than, 'I have no idea if or when I'll be able to implement that for you'.

@rvanbaalen

This comment has been minimized.

Show comment
Hide comment
@rvanbaalen

rvanbaalen Jun 6, 2016

I am completely with @bcjarrett here. Other companies with similar or smaller development teams & budget can develop entire applications in the time we have been waiting for 'just' an API.

I too have to keep disappointing users that 'Basecamp 3 isn't supported yet' and 'We don't know when we can support it'.

rvanbaalen commented Jun 6, 2016

I am completely with @bcjarrett here. Other companies with similar or smaller development teams & budget can develop entire applications in the time we have been waiting for 'just' an API.

I too have to keep disappointing users that 'Basecamp 3 isn't supported yet' and 'We don't know when we can support it'.

@raulpopadineti

This comment has been minimized.

Show comment
Hide comment
@raulpopadineti

raulpopadineti Jun 6, 2016

Most certainly they're too focused on other things. They don't feel like it's such an important thing to invest since it's not affecting their business directly (only with a small decrease in reputation from us).

Until they find some time to get this API version out in the public, they'll still tell us "it's done when it's done". We can't do anything else than wait.

If someone would be dedicated 100% of the time on this (from their side), there's no way you can't estimate an ETA.

raulpopadineti commented Jun 6, 2016

Most certainly they're too focused on other things. They don't feel like it's such an important thing to invest since it's not affecting their business directly (only with a small decrease in reputation from us).

Until they find some time to get this API version out in the public, they'll still tell us "it's done when it's done". We can't do anything else than wait.

If someone would be dedicated 100% of the time on this (from their side), there's no way you can't estimate an ETA.

@javan

This comment has been minimized.

Show comment
Hide comment
@javan

javan Jun 6, 2016

Member

Hi all, once again I'm sorry for the delay. We have not done a good job communicating our progress.

Nick left Basecamp, and it's taken me a while to get up to speed with the project. The transition happened at a particularly busy time (company meetup, RailsConf, and welcoming in a class of interns) so I wasn't able to really dig in until recently. You have my full attention now 😁.

One of the challenges we're still working through is how to handle file attachments with Basecamp 3's API. I'll explain.

In Basecamp 2, to create a message with attachments using the API, you simply pass an array of attachments params along with the message params. Basecamp 2 displays all attachments below the content its associated with so the whole process is pretty straightforward.

In Basecamp 3, files can be attached anywhere. You can drop a file in a message and it renders right where you dropped it. The experience is great and it enables users to compose much richer content than they could in Basecamp 2. Translating that experience to the API is where things get tricky. Instead of looking for attachments params, we need to scan the content for attachments, extracting the location and identifying attributes along the way. We don't expect API consumers to construct the full set of HTML it takes to render an attachment so we're working on a well defined, minimal HTML structure that will be seamlessly serialized on the way in and out.

We actually have two programmers working on the attachments API, and I'm cruising along to finish up everything else. I don't want to make promises I can't keep, but I suspect the API will be publicly available in 4-6 weeks.

Today I gave 75 more people beta access to the API. That's everyone in the backlog. If you're interested in early access, submit your request here: https://basecamp.wufoo.com/forms/request-early-access-to-the-basecamp-3-api/. I'll be granting access more frequently now.

Thanks for your time,
-Javan

Member

javan commented Jun 6, 2016

Hi all, once again I'm sorry for the delay. We have not done a good job communicating our progress.

Nick left Basecamp, and it's taken me a while to get up to speed with the project. The transition happened at a particularly busy time (company meetup, RailsConf, and welcoming in a class of interns) so I wasn't able to really dig in until recently. You have my full attention now 😁.

One of the challenges we're still working through is how to handle file attachments with Basecamp 3's API. I'll explain.

In Basecamp 2, to create a message with attachments using the API, you simply pass an array of attachments params along with the message params. Basecamp 2 displays all attachments below the content its associated with so the whole process is pretty straightforward.

In Basecamp 3, files can be attached anywhere. You can drop a file in a message and it renders right where you dropped it. The experience is great and it enables users to compose much richer content than they could in Basecamp 2. Translating that experience to the API is where things get tricky. Instead of looking for attachments params, we need to scan the content for attachments, extracting the location and identifying attributes along the way. We don't expect API consumers to construct the full set of HTML it takes to render an attachment so we're working on a well defined, minimal HTML structure that will be seamlessly serialized on the way in and out.

We actually have two programmers working on the attachments API, and I'm cruising along to finish up everything else. I don't want to make promises I can't keep, but I suspect the API will be publicly available in 4-6 weeks.

Today I gave 75 more people beta access to the API. That's everyone in the backlog. If you're interested in early access, submit your request here: https://basecamp.wufoo.com/forms/request-early-access-to-the-basecamp-3-api/. I'll be granting access more frequently now.

Thanks for your time,
-Javan

@cbaci

This comment has been minimized.

Show comment
Hide comment
@cbaci

cbaci Jun 22, 2016

@javan, thanks for picking it up. Change being the only constant is difficult on timelines! As we build out our integration, we're finding that it'd be great to have some form of master json schema document to aid in building out persistence model. Is it too forward to ask if such a thing exists? Grepping through the .md files to build out our integrated db structure is cumbersome.

cbaci commented Jun 22, 2016

@javan, thanks for picking it up. Change being the only constant is difficult on timelines! As we build out our integration, we're finding that it'd be great to have some form of master json schema document to aid in building out persistence model. Is it too forward to ask if such a thing exists? Grepping through the .md files to build out our integrated db structure is cumbersome.

@garek007

This comment has been minimized.

Show comment
Hide comment
@garek007

garek007 Jul 6, 2016

It sounds like we still don't have an API yet? I guess I'll apply for early access...

garek007 commented Jul 6, 2016

It sounds like we still don't have an API yet? I guess I'll apply for early access...

@rafo

This comment has been minimized.

Show comment
Hide comment
@rafo

rafo Jul 7, 2016

At least, they changed their communication behavior 👎

@javan: "We have not done a good job communicating our progress"

rafo commented Jul 7, 2016

At least, they changed their communication behavior 👎

@javan: "We have not done a good job communicating our progress"

@javan

This comment has been minimized.

Show comment
Hide comment
@javan

javan Jul 8, 2016

Member

The Basecamp 3 API will officially launch on July 20. Thanks for hanging in there everyone!

Member

javan commented Jul 8, 2016

The Basecamp 3 API will officially launch on July 20. Thanks for hanging in there everyone!

@javan

This comment has been minimized.

Show comment
Hide comment
@javan

javan Jul 20, 2016

Member

🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀

🚀 https://github.com/basecamp/bc3-api 🚀

🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀

Member

javan commented Jul 20, 2016

🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀

🚀 https://github.com/basecamp/bc3-api 🚀

🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀🚀

@javan javan closed this Jul 20, 2016

@wraybowling

This comment has been minimized.

Show comment
Hide comment
@wraybowling

wraybowling Jul 20, 2016

I love that I was reading this thread today, and that the API came out today. I love a happy ending.

wraybowling commented Jul 20, 2016

I love that I was reading this thread today, and that the API came out today. I love a happy ending.

@jdsimcoe

This comment has been minimized.

Show comment
Hide comment

jdsimcoe commented Jul 20, 2016

Woohoo!!! 🎉 🎉 🎉 https://www.producthunt.com/tech/basecamp-3-api

@garek007

This comment has been minimized.

Show comment
Hide comment
@garek007

garek007 Jul 20, 2016

yeeesss!!!!

garek007 commented Jul 20, 2016

yeeesss!!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment