-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Documentation on the http-based Worker Replication service
- Loading branch information
1 parent
a235713
commit 91b3c7e
Showing
5 changed files
with
641 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
.. note:: | ||
|
||
Information in this guide corresponds to the version **40** of the Qserv REST API. Keep in mind | ||
that each implementation of the API has a specific version. The version number will change | ||
if any changes to the implementation or the API that might affect users will be made. | ||
The current document will be kept updated to reflect the latest version of the API. | ||
|
||
############################## | ||
The internal REST API of Qserv | ||
############################## | ||
|
||
.. toctree:: | ||
:maxdepth: 2 | ||
|
||
introduction | ||
repl-worker |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
.. _qserv-api-introduction: | ||
|
||
Introduction | ||
============ | ||
|
||
This document presents a collection of the internal REST APIs that exist in the Qserv implementation. | ||
Qserv developers may use these APIs to interact with various components of Qserv. | ||
|
||
The Qserv REST API is a collection of RESTful web services that provide access to various components of the Qserv system. | ||
The API enforeces a specific interaction model between the client and the server. The following hihglites are worth mentioning: | ||
|
||
- All ``POST``, ``PUT`` and ``DELETE`` requests must be accompanied by a JSON payload. | ||
- Responses of all but a few select services are in JSON format.Exceptions are documented in the API documentation. | ||
- Schemas of the JSON requests and payloads are defined in the API documentation. | ||
- The API is versioned. The version number is included in the URL path of the ``GET`` requests, and it's | ||
inluded into the JSON payload of the ``POST``, ``PUT`` and ``DELETE`` requests. | ||
- All API services are protected by an authentication mechanism. The client must provide a valid | ||
authentication token in the JSON payload of the the ``POST``, ``PUT`` and ``DELETE`` requests. | ||
No authentication is required for the ``GET`` requests. | ||
|
||
The general information on the structure of the API can be found in the following document: | ||
|
||
- :ref:`ingest-general` | ||
|
||
The rest of the current document provides detailed information on the individual services that are available in the Qserv API. |
Oops, something went wrong.