# How can I use the SharePoint Javascript Object Model from a plain HTML page?

I would like to use the SharePoint Javascript Object Model from a "plain" html page (ie, not an .aspx application page etc.) Is this even possible? If so, what scripts should I reference? I've added the following:

  <script type="text/ecmascript" src="/_layouts/SP.js" />
<script type="text/ecmascript" src="/_layouts/SP.Core.js" />
<script type="text/ecmascript" src="/_layouts/SP.Debug.js" />
<script type="text/ecmascript" src="/_layouts/SP.Runtime.Debug.js" />


But when the page loads, I get a 'Type is not defined' error in SP.js and SP.Core.js. Note this is from within the SP site, so this isn't a cross-domain issue.

The SharePoint JavaScript client object model only works on pages that are a part of the SharePoint framework (i.e. in Web Parts, Application Pages, etc.). This tutorial makes mention of that: http://www.codeproject.com/Articles/60348/SharePoint-2010-Client-Object-Model-for-JavaScript.aspx

• You could, however, write a custom REST or AJAX web service that does the calls for you and then you could access those from your JavaScript. – John Chapman Nov 6 '11 at 1:08
• I actually got it 'almost working', but SP.js definitely depends on some markup and other scripts only found in application pages. REST and Ajax against the built-in listdata.svc, etc. is what I landed on, though I'm not sure I'll be able to get at everything I would have liked (like SPWeb.Navigation). – Daniel Nov 7 '11 at 2:34

This is what I used to fix this problem:

<SharePoint:ScriptLink Name="MicrosoftAjax.js" runat="server" Defer="False" Localizable="false"/>


I added the above ScriptLinks in this order, and defered both the MicrosoftAjax.js and SP.Core.js includes, and delayed the SP.js. The SP.js file has dependencies in the preceding includes that requires it to be delayed.

• this would not work on a plain html page, just a .aspx – Daniel Mar 27 '14 at 19:54
• This works perfectly on custom aspx pages – Jake Nov 13 '18 at 7:08
<SharePoint:ScriptLink Name="SP.js" runat="server" OnDemand="true" Localizable="false" />


will do the work.

You are missing init.js.

Add it just like the rest of the scripts you have referenced and you should stop getting the dependency errors.

• Can't seem to get this one to work, still getting the dependency errors on SP2010. Any tips? Should it be <script type="text/ecmascript" src="/_layouts/init.js" />? – MattV Dec 6 '16 at 9:54
• @MattV It's been a while since I was doing this work and I don't have access to it so I can't just look it up for you. That is generally the idea though. Sorry I can't be of more help. Maybe check to make sure that is the actual path of your init.js. – robschimmel Dec 11 '16 at 21:49

The JSOM uses the Type.registerNamespace method in the Microsoft Ajax library to register the SP namespace. Use the following code to add a reference to the Microsoft Ajax library from your page: <script type="text/javascript" src="//ajax.aspnetcdn.com/ajax/4.0/1/MicrosoftAjax.js"></script>