Request Collection

The request collection is the primary configuration for Slumber. It defines which requests can be made, and how to make them. When running a slumber instance, a single collection file is loaded. If you want to work with multiple collections at once, you'll have to run multiple instances of Slumber.

Collection files are designed to be sharable, meaning you can commit them to your Git repo. The most common pattern is to create one collection per API repo, and check it into the repo so other developers of the API can use the same collection. This makes it easy for any new developer or user to learn how to use an API.

Format & Loading

A collection is defined as a YAML file. When you run slumber, it will search the current directory for the following default collection files, in order:

  • slumber.yml
  • slumber.yaml
  • .slumber.yml
  • .slumber.yaml

Whichever of those files is found first will be used. If you want to use a different file for your collection (e.g. if you want to store multiple collections in the same directory), you can override the auto-search with the --collection (or -c) command line argument. E.g.:

slumber -c my-collection.yml

Collection History & Migration

Each collection needs a unique ID generated when the collection is first loaded by Slumber. This ID is used to persist request history and other data related to the collection. If you move a collection file, a new ID will be generated and it will be unlinked from its previous history. If you want to retain that history, you can migrate data from the old ID to the new one like so:

slumber collections migrate /slumber/old.yml /slumber/new.yml

If you don't remember the path of the old file, you can list all known collections with:

slumber collections list


A request collection supports the following top-level fields:

profilesmapping[string, Profile]Static template values[]
requestsmapping[string, RequestRecipe]Requests Slumber can send[]
chainsmapping[string, Chain]Complex template values[]


    name: Local
      host: http://localhost:5000
      user_guid: abc123
    name: Production
      user_guid: abc123

    source: !file ./username.txt
    source: !prompt Password
    sensitive: true
    source: !request login
    selector: $.token

# Use YAML anchors for de-duplication
base: &base
    Accept: application/json
    Content-Type: application/json

    <<: *base
    method: POST
    url: "{{host}}/anything/login"
    body: |
        "username": "{{chains.username}}",
        "password": "{{chains.password}}"

    <<: *base
    method: GET
    url: "{{host}}/anything/current-user"
      auth: "{{chains.auth_token}}"