Node.js client for the Swiftype API
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
fixtures/api.swiftype.com-443 Changes based on feedback. Updated readme, removed semicolon, reverte… Oct 1, 2018
lib Changes based on feedback. Updated readme, removed semicolon, reverte… Oct 1, 2018
test Changes based on feedback. Updated readme, removed semicolon, reverte… Oct 1, 2018
.gitignore Update package.json May 23, 2014
.nvmrc Added .nvmrc and package-lock.json Oct 15, 2018
.travis.yml Removing "official" support for node versions < 4 Sep 26, 2018
LICENSE Rich license Feb 1, 2019
README.md
logo-site-search.png Adds fancy README. Feb 1, 2019
package-lock.json Added .nvmrc and package-lock.json Oct 15, 2018
package.json Release 0.4.0 Oct 15, 2018

README.md

Elastic Site Search Logo

Travis build GitHub release

A first-party Node client for the Elastic Site Search API.

Contents


Getting started 🐣

With npm:

npm install swiftype

or clone locally:

$ git clone git@github.com:swiftype/swiftype-node.git
$ cd swiftype-node
$ npm install

Usage

Create a new instance of the client with your api key:

var SwiftypeApi = require('swiftype')
var swiftype = new SwiftypeApi({
  apiKey: 'yourApiKey'
})

Searching

Search for cats on the engine my-engine with filters and facets:

swiftype.search({
  engine: 'my-engine',
  q: 'cats',
  filters: {
    page: {
      'enumField': 'theFilter'
    }
  },
  facets: {
    page: ['enumField', 'anotherField']
  }
}, function(err, res) {
  console.log(res)
})

Autocomplete

Autocomplete suggestion for cat on the engine my-engine with filters:

swiftype.suggest({
  engine: 'my-engine',
  q: 'cat',
  filters: {
    page: {
      'enumField': 'theFilter'
    }
  }
}, function(err, res) {
  console.log(res)
})

Click

Log clickthrough for cat on the engine my-engine for the documentType page:

swiftype.click({
  engine: 'my-engine',
  q: 'cat',
  id: 'the-document-id',
  documentType: 'page'
}, function(err, res) {
  console.log(res)
})

Documents

Create a new document:

swiftype.documents.create({
  engine: 'my-engine',
  documentType: 'books',
  document: {
    external_id: '1',
    fields: [
      { name: 'title', value: 'The Great Gatsby', type: 'string' },
      { name: 'author', value: 'F. Scott Fitzgerald', type: 'string' },
      { name: 'genre', value: 'fiction', type: 'enum' }
    ]
  }
}, function(err, res) {
  console.log(res)
})

Engines

Fetch all of your engines:

swiftype.engines.list(function(err, res) {
  console.log(res)
})

Fetch a single engine:

swiftype.engines.get({
  engine: 'my-engine'
}, function(err, res) {
  console.log(res)
})

Document Types

Fetch all of the document types in the engine my-engine

swiftype.documentTypes.list({
  engine: 'my-engine'
}, function(err, res) {
  console.log(res)
})

Fetch the document type books in the engine my-engine

swiftype.documentTypes.get({
  engine: 'my-engine',
  documentType: 'books'
}, function(err, res) {
  console.log(res)
})

Check out the tests for more examples!

Running tests

$ npm test

The tests use stubbed HTTP interactions that are recorded with the node-replay module. By default, HTTP interactions are not allowed when running the tests.

The tests can also use environment variables so that you can create new replays against your own account. Don't forget to change the "authorization" header in the replay files to not give away your api key.

  • SWIFTYPE_TEST_MY_ENGINE = the slug for your 'my-engine' in the tests
  • SWIFTYPE_TEST_BOOKSTORE_ENGINE = the slug for your 'bookstore' in the tests
  • SWIFTYPE_TEST_TEMPORARY_ENGINE = the slug for your 'temporary' in the tests
  • SWIFTYPE_TEST_API_KEY = your api key in the tests
  • REPLAY = 'record' to record new replay files

FAQ 🔮

Where do I report issues with the client?

If something is not working as expected, please open an issue.

Where can I learn more about Site Search?

Your best bet is to read the documentation.

Where else can I go to get help?

You can checkout the Elastic Site Search community discuss forums.

Contribute 🚀

We welcome contributors to the project. Before you begin, a couple notes...

License 📗

MIT © Elastic

Thank you to all the contributors!