Ready to take your JavaScript development to the next level? Meet npm Enterprise - the ultimate in enterprise JavaScript. Learn more »


2.1.3 • Public • Published

sp-request - simplified SharePoint HTTP client


Circle CI Coverage Status npm version

Need help on SharePoint with Node.JS? Join our gitter chat and ask question! Gitter chat

If you are looking for a way to perform some REST queries against SharePoint, consider also PnP-JS-Core with node.js integration

sp-request based on request-promise (promise-aware implementation of request) and node-sp-auth modules. node-sp-auth implements different authentication options for unattended SharePoint authentication from nodejs. You can send REST queries to SharePoint (works with both on-prem and online) using well-known request syntax with the same params that request supports, and sp-request (with help of node-sp-auth) takes care about authenticating you inside SharePoint. Responses implemented using modern promise-style approach.

Versions supported:

  • SharePoint 2013, 2016
  • SharePoint Online

How to use:


npm install sp-request --save-dev

Create sprequest function:

import * as sprequest from 'sp-request';
let spr = sprequest.create(credentialOptions);
Get list by title:
  .then(response => {
    console.log('List Id: ' + response.body.d.Id);
  .catch(err =>{
    console.log('Ohhh, something went wrong...');
Update list title:
  .then(digest => {
    return'http://sp2013dev/sites/dev/_api/web/lists/GetByTitle(\'TestList\')', {
      body: {
        '__metadata': { 'type': 'SP.List' },
        'Title': 'TestList'
      headers: {
        'X-RequestDigest': digest,
        'X-HTTP-Method': 'MERGE',
        'IF-MATCH': '*'
  .then(response => {
    if (response.statusCode === 204) {
      console.log('List title updated!');
  }, err => {
    if (err.statusCode === 404) {
      console.log('List not found!');
    } else {

... as simple as that! A bit more samples you can find under integration tests


[main sp-request export].create(credentialOptions):

  • credentialOptions: optional, object containing credentials. Since version 2.x sp-request relies on node-sp-auth module for authentication. You can find description for credentialOptions under node-sp-auth.

Call to sprequest.create(credentialOption) returns sprequest function with predefined authentication. You can use this function later to send REST queries (like in samples above) without specifying credentials again.


  • options: required, settings object for request module. For all available values refer to the original request docs

By default sp-request sets following params for request:

    json: true,
    strictSSL: false, /* bypassing SSL validation errors */
    headers: {
        'Accept': 'application/json;odata=verbose',
        'Content-Type': 'application/json;odata=verbose'

as a result you can access body.d property as an object. You can provide your own headers and override defaults if it's required. The only difference from original request, that sp-request returns Bluebird's Promise (ES2015 promise implementation), instead of relying on callbacks. So you can combine multiple requests in a convenient and readable way.


  • url - required, string site url

Returns request digest as string via promise.

Convenience methods:

sprequest(url, options):

  • url - required, string
  • options - required, request options object

The same as sprequest(options) but options.url will be equal to the first param.

sprequest.get(url, options)

  • url - required, string
  • options - optional, request options object

The same as sprequest(options) but options.url will be equal to the first param and options.method: 'GET'., options)

  • url - required, string
  • options - optional, request options object

The same as sprequest(options) but options.url will be equal to the first param and options.method: 'POST'.

Supplying additional headers via environment variables

Sometimes you need to push additional headers for sp-request without direct access to sp-requests object. For example from third party module, which uses sp-request internally. For that purpose you can use environmental variables. Provide it in a below way:

process.env['_sp_request_headers'] = JSON.stringify({


I recommend using VS Code for development. Repository already contains some settings for VS Code editor.

Before creating Pull Request you need to create an appropriate issue and reference it from PR.

  1. git clone
  2. npm run build - restores dependencies and runs typescript compilation
  3. gulp live-dev - setup watchers and automatically runs typescript compilation, tslint and tests when you save files


  1. npm test. As a result /reports folder will be created with test results in junit format and code coverage. Additionally test reports will be available in a console window.

Integration testing:

  1. Rename file /test/integration/config.sample.ts to config.ts.
  2. Update information in config.ts with appropriate values (urls, credentials, environment).
  3. Run gulp test-int.


npm i sp-request

Downloadsweekly downloads









last publish


  • avatar
Report a vulnerability