Where to SET the API domain?

7 posts / 0 new
Last post
- -
Joined: 2012-08-20
Aug 20, 2012
Where to SET the API domain?

Guys,

Where do I set up the API domain in the LinkedIn panels? I've been trying to find out exactly *where* this is set in LinkedIn as the new app I just created is throwing a JS error:

"You must specify a valid JavaScript API Domain as part of this key's configuration."

Looking at this page, I follow the "Setting your API Domain" link:

http://developer.linkedinlabs.com/tutorials/jsapi_authentication/

But then I get a 404, page not found... any info on this?

Regards

Jeroen Koomen's picture
Joined: 2011-08-11
Feb 22, 2013

You have to add the domain in the API key configuration page for your app. I assume you already created an API key for your app. If not, see the documentation on how to do this. See http://developer.linkedin.com/javascript
To set the domain go to https://www.linkedin.com/secure/developer
Hope this helps.

Simon Thompson's picture
Joined: 2013-04-08
Apr 11, 2013

I too found this very confusing... adding your "website name" isn't the domain API that the function is looking for. When you create the API, the last box before you accept the "terms and conditions" is the box where you can add in the domain name e.g. http://www.example.com

It would be great if there was an "*" on this field.

I did this and it fixed in instantly. You can also put in localhost in here too. like: http://localhost/

Jonathan Guan's picture
Joined: 2013-02-20
Apr 26, 2013

Thanks Simon, your advice did the trick.

Ara Rubyan's picture
Joined: 2013-04-19
Aug 22, 2013

Hey, Simon, it worked for me too. That one asterisk made all the difference. Thanks!

Scott Drummonds's picture
Joined: 2013-10-29
Jan 12, 2014

Simon Thompson, you are a genius and saved me a day of work. Thanks for posting this fix. I was also confused and thinking my Javascript domain should be set in the "Website URL" field. I went to the bottom of the page as you suggested and things work great.

Joined: 2014-02-17
Feb 18, 2014

thanks Simon... Put it like this http://localhost/*