There are a lot of resources around that show how to do this, but I couldn’t find a comprehensive go-to link, so here we are.

You can create a SharePoint site using the REST API.  Here’s a fully baked example:

<!--
    SiteRequestForm.html: Collect information and create a site for the user.
-->

<center>
<table>
    <tr>
        <td>Site Name:</td>
        <td><input type="text" name="SiteName" id="SiteName" /></td>
    </tr>
    <tr>
        <td colspan="2">
            <input type="submit" id="CreateSiteButton" value="Create the Site" />
        </td>
    </tr>
</table>
</center>

<script src="../Plugins/jquery-1.11.0.min.js"></script>

<script>
var CreateSiteLogicContainer = {

    createSiteData: {
            "parameters": {
                __metadata: { "type": "SP.WebInfoCreationInformation" },
                Url: "Paultest1",
                Title: "Paultest1",
                Description: "rest-created web by Paul!",
                Language: 1033,
                WebTemplate: "sts",
                UseUniquePermissions: false
            }
    },

    createSite: function () {

        jQuery.support.cors = true;

        CreateSiteLogicContainer.createSiteData.parameters.Url = $("#SiteName").val();
        
        $.ajax({
            url: "https://bigapplesharepoint.sharepoint.com/NBAIADev/_api/web/webinfos/add",
            method: "POST",

            headers: {
                "Accept": "application/json; odata=verbose",
                "content-type": "application/json;odata=verbose",
                "X-RequestDigest": $("#__REQUESTDIGEST").val()
            },

            data: JSON.stringify(CreateSiteLogicContainer.createSiteData),

            success: function () { alert("success"); },
            error: function () { alert("error"); }

        });
    },

    wireUpForm: function () {
        $("#CreateSiteButton").click(function () {
            alert("About to try and create the site.");
            CreateSiteLogicContainer.createSite();
        });
    }


}

CreateSiteLogicContainer.wireUpForm();

</script>

When successful, you get a JSON packet in response like this:

My key thoughts and learnings from this include:

• This approach uses jQuery.  In my case, my jQuery library is located in “../plugins.”  You’ll want to change that to point to your favorite JQ location.
• You can copy and paste that whole snippet into a Content Editor Web Part on a page and it should work just fine.  You’ll want to change the end point of the API call and make sure you reference JQ correctly.
• The URL is relative to your API’s endpoint.  In my case, it’s creating sub-sites underneath https://bigapplesharepoint.com
• You don’t need to provide a content-length. Some blog posts and MSDN document implies that you do, but happened for me automatically, which I assume is being handled by the $.ajax call itself.
• This line is required in order to avoid a “forbidden” response: "X-RequestDigest": $("#__REQUESTDIGEST").val().  There are other ways to do it, but this is pretty nice.  I have lost the link to blog that provided this shortcut.  H/T to you, mysterious blogger!

Good luck and hope this helps someone out.

</end>

Subscribe to my blog.

Follow me on Twitter at http://www.twitter.com/pagalvin

I’ve been working on a public facing web site for my SharePoint practice here in New York and it uses a lot of JavaScript and REST calls to show content.

During mainline development, I create a small dataset with just 10 or so rows in a custom list and my REST calls all pulled from there.  Once I bumped up the list to have a few hundred rows of data to test for anticipated growth, I found that I was getting exactly 100 rows returned back on my REST calls.

This is a very simple thing to address.  In my case (and I believe in most cases), the default REST calls to SharePoint (and possibly as an industry standard?) return 100 rows.  To return more than the default, use the $top parameter on your call, as in:

GET /Insights%20Dev/_api/web/lists/GetByTitle(‘MockBlog’)/items?$select=ID,Title,Categories/Title,Blog_x0020_Author/Title,DatePublished,BlogSummary&$expand=Blog_x0020_Author,Categories&$filter=&$top=9999

I picked 9999 in this case since I know that growth-wise, there won’t be more than 200 or so rows added to this list in a year.  If it becomes ungainly, we can implement some paging down the road.

</end>

Subscribe to my blog.

Follow me on Twitter at http://www.twitter.com/pagalvin