Skip to content
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

Changed to use new API environment. #14

Closed
wants to merge 1 commit into from
Closed

Conversation

glub
Copy link

@glub glub commented Aug 30, 2017

The API endpoint has been updated on Behance to live at adobe.io. All new API keys granted from Adobe must run thru this environment otherwise they won't work.

It should be backwards compatible, but please check with the older api keys.

@coveralls
Copy link

Coverage Status

Coverage decreased (-5.0%) to 93.333% when pulling 83fa458 on glub:master into e63d11d on Polyneue:master.

@Polyneue
Copy link
Owner

Hi @glub, thanks for the contribution!

Do you have any documentation or helpful links around this change on the Adobe side? I went over to the Adobe IO site but couldn't find anything useful around their Behance API updates.

@Polyneue Polyneue self-requested a review August 30, 2017 21:59
@glub
Copy link
Author

glub commented Aug 30, 2017

@Polyneue The only public references can be found here:
https://www.behance.net/developer/documentation/overviewAuthentication
https://www.behance.net/developer/documentation/overviewEnvironments

The first link under the header, IMS Client Authentication refers to the api_key parameter, and the second link refers to the environment base URLs.

@Polyneue
Copy link
Owner

@glub are you in a beta program for Adobe? Neither of those links work for me when trying to access them.

screen shot 2017-08-30 at 6 14 20 pm

@glub
Copy link
Author

glub commented Aug 30, 2017

Ah, how interesting... I work for Adobe and, when I drop off their network, sure enough those documents disappear. What's even more strange is I spoke to the Behance team yesterday and the suggested I make a fork, and I said I would push the changes back up (which they were cool with). But, it appears, it's not publicly announced yet. Hmm.

@Polyneue
Copy link
Owner

Thanks for the heads up! I'll keep checking on those links over the next couple of days and once they're live, I'll get the module tested and deployed.

Cool to see that open source projects get noticed by you guys 👍

@Polyneue
Copy link
Owner

Polyneue commented Feb 2, 2018

Closing this since there hasn't been any new information around an API change. Definitely re-open if this officially launches!

@Polyneue Polyneue closed this Feb 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants