Registration API

Authentication

The Registry requires requests to the Registration API to be authenticated. The Registration API implements Basic HTTP Authentication, as defined by RFC 2617, which enables a client to authenticate individual HTTP requests by including an authentication header in the request. In order to make authorized calls to the API, your application must first obtain an access token, and use that token in the authentication header of all subsequent requests.

A Simplified RESTful workflow

API clients and the Registry communicates over HTTPS, exchanging JSON representations of API objects.

This simplified example of a RESTful workflow includes requests to register remote track hubs, list registered track data hubs with the Registry and update a registered track hub.

These examples assume the track hub data provider using the API has signed up and created an account with the Registry. To create an account, go to registration.

Logging in

All requests to the service must be authenticated. The first step in any Registration API RESTful workflow is to obtain an authentication token.

Registering track hubs

You've just signed up and you've got some remote public track hubs that you want to register with and make available for search on the Track Hub Registry.

Retrieve the list of registered track hubs

You've submitted some of your public track hubs to the Registry. You want to know which ones by retrieving the list of registered track hubs from the Registry.

Update registered track hubs

You've updated the structure or content of one of your remote public hubs registered with us. You obviously want the changes to appear on the Registry as well.

Delete registered track hubs

One of your remote public hubs does not exist any more. Or you simply don't want to make it available for search in the Track Hub Registry.

Log out

This terminates the client session and ends any possible workflow of interaction between the client and the Registration API.