<NME> readme.markdown
<BEF> ![Traverson Logo](https://raw.githubusercontent.com/traverson/traverson/master/misc/logo/traverson-logo.72dpi.png)

Traverson
=========

A Hypermedia API/HATEOAS Client for Node.js and the Browser
-----------------------------------------------------------

[![Node CI Workflow Status][github-actions-ci-badge]][github-actions-ci-link]
![node][node-badge]
[![NPM](https://nodei.co/npm/traverson.png?downloads=true&stars=true)](https://nodei.co/npm/traverson/)
[![Greenkeeper badge](https://badges.greenkeeper.io/traverson/traverson.svg)](https://greenkeeper.io/)

| File Size (browser build) | KB |
|---------------------------|---:|
| minified & gzipped        | 17 |
| minified                  | 61 |


Quick Links
-----------

* [Installation](https://github.com/traverson/traverson/blob/master/user-guide.markdown#installation)
* [User Guide](https://github.com/traverson/traverson/blob/master/user-guide.markdown)
* [API reference documentation](https://github.com/traverson/traverson/blob/master/api.markdown)
* [Release Notes](https://github.com/traverson/traverson/blob/master/CHANGELOG.md)
* [Contributing to Traverson](https://github.com/traverson/traverson/blob/master/CONTRIBUTING.md)
* [Code of Conduct](https://github.com/traverson/traverson/blob/master/CODE_OF_CONDUCT.md)

Introduction
------------

Traverson comes in handy when consuming REST APIs that follow the HATEOAS principle, that is, REST APIs that have links between their resources. Such an API (also sometimes referred to as hypermedia or hypertext-driven API) typically has a root resource/endpoint, which publishes links to other resources. These resources in turn might also have, as part of their metadata, links to related resources. Sometimes you need to follow multiple consecutive links to get to the resource you want. This pattern makes it unnecessary for the client to hardcode all endpoint URLs of the API it uses, which in turn reduces the coupling between the API provider and the API consumer. This makes it easier for the API provider to change the structure of the API without breaking existing client implementations.

To follow a path of links you typically start at one URL (most often the root URL of the API), then look for the link you are interested in, fetch the document from there and repeat this process until you have reached the end of this path.

Traverson does that for you. You just need to tell Traverson where it can find the link to follow in each consecutive document and Traverson will happily execute the hops from document to document for you and when it's done, hand you the final http response or document, the one you really wanted to have in the first place.

Traverson works in Node.js and in the browser. For now, Traverson only supports JSON APIs. Support for other specialized JSON hypermedia types can be added with plug-ins (for example JSON-HAL).


The most basic thing you can do with traverson is to let it start at the root URL of an API, follow some links and pass the resource that is found at the end of this journey back to you. We call this procedure a *"link traversal process"*. Here's how:
    * [AngularJS](#angularjs)
* [Documentation](#documentation)
    * [Following Links](#following-links)
    * [Configuring Traverson](#configuring-traverson-the-request-builder-object)
    * [Get Full HTTP Response](#more-control-receive-the-full-http-response)
    * [Pass Links as Array](#pass-a-link-array)
    * [POST, PUT, DELETE and PATCH](#post-put-delete-and-patch)
    * [Error Handling](#error-handling)
    * [Absolute Versus Relative URLs](on-absolute-urls-absolute-url-paths-and-relative-url-paths)
    * [JSONPath](#jsonpath)
    * [URI Templates](#uri-templates)
    * [Headers and Authentication](#headers-http-basic-auth-oauth-and-whatnot)
    console.log(JSON.stringify(document))
  }
});
```

The [User Guide](https://github.com/traverson/traverson/blob/master/user-guide.markdown) has a ton of examples of what else Traverson can do for you. Here are some highlights:

* resolve URI Templates
* use JSONPath
* manage headers, query strings and authentication (including OAuth)
* content type detection
* work with different media types by using plug-ins
* use a custom JSON parser
* continuing link traversals

License
-------

MIT

[github-actions-ci-link]: https://github.com/traverson/traverson/actions?query=workflow%3A%22Node.js+CI%22+branch%3Amaster

[github-actions-ci-badge]: https://github.com/traverson/traverson/workflows/Node.js%20CI/badge.svg

[node-badge]: https://img.shields.io/node/v/traverson.svg?logo=node.js
This would register `MasonAdapter` as a plug-in for the media type `application/vnd.mason+json`. `MasonAdapter` would need to be a constructor function adhering to the constraints given in [the next subsection](#implementing-media-type-plug-ins).

Once registered, a media type plug-in is automatically eligible for [content negotiation](#content-negotiation). You can also force Traverson to use a media type by calling `setMediaType`. To force Traverson to use the `MasonAdapter` no matter which `Content-Type` header the server sets, you would call `setMediaType(application/vnd.mason+json)`.

Usually, a media type plug-in should also provide a `mediaType` property containing the registered media type it is intended for. Thus, the example above could be simplified to


<MSG> correct links

[skip ci]

<DFF> @@ -43,12 +43,12 @@ Table of Contents
     * [AngularJS](#angularjs)
 * [Documentation](#documentation)
     * [Following Links](#following-links)
-    * [Configuring Traverson](#configuring-traverson-the-request-builder-object)
+    * [Configuring Traverson](#configuring-traverson--the-request-builder-object)
     * [Get Full HTTP Response](#more-control-receive-the-full-http-response)
     * [Pass Links as Array](#pass-a-link-array)
     * [POST, PUT, DELETE and PATCH](#post-put-delete-and-patch)
     * [Error Handling](#error-handling)
-    * [Absolute Versus Relative URLs](on-absolute-urls-absolute-url-paths-and-relative-url-paths)
+    * [Absolute Versus Relative URLs](#on-absolute-urls-absolute-url-paths-and-relative-url-paths)
     * [JSONPath](#jsonpath)
     * [URI Templates](#uri-templates)
     * [Headers and Authentication](#headers-http-basic-auth-oauth-and-whatnot)
@@ -519,7 +519,7 @@ traverson.registerMediaType('application/vnd.mason+json', MasonAdapter);
 
 This would register `MasonAdapter` as a plug-in for the media type `application/vnd.mason+json`. `MasonAdapter` would need to be a constructor function adhering to the constraints given in [the next subsection](#implementing-media-type-plug-ins).
 
-Once registered, a media type plug-in is automatically eligible for [content negotiation](#content-negotiation). You can also force Traverson to use a media type by calling `setMediaType`. To force Traverson to use the `MasonAdapter` no matter which `Content-Type` header the server sets, you would call `setMediaType(application/vnd.mason+json)`.
+Once registered, a media type plug-in is automatically eligible for [content negotiation](#content-type-detection-versus-forcing-media-types). You can also force Traverson to use a media type by calling `setMediaType`. To force Traverson to use the `MasonAdapter` no matter which `Content-Type` header the server sets, you would call `setMediaType(application/vnd.mason+json)`.
 
 Usually, a media type plug-in should also provide a `mediaType` property containing the registered media type it is intended for. Thus, the example above could be simplified to
 

{'addition_count': 3, 'commit_subject': 'correct links', 'deletion_count': 3, 'file_extension': '.markdown', 'lang': 'markdown', 'license': 'mit', 'repo_name': 'traverson/traverson'}