You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/_openvox-server_8x/http_api_index.markdown
+33-34Lines changed: 33 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,12 +25,12 @@ All configuration endpoints are prefixed with `/puppet`, while all CA endpoints
25
25
26
26
### Authorization
27
27
28
-
Authorization for `/puppet` and `/puppet-ca` endpoints is controlled with [OpenVox Server's `auth.conf` authorization system](./config_file_auth.html).
28
+
Authorization for `/puppet` and `/puppet-ca` endpoints is controlled with [OpenVox Server's `auth.conf` authorization system](config_file_auth.html).
29
29
30
30
## OpenVox V3 HTTP API
31
31
32
32
The OpenVox agent application uses several network services to manage systems. These services are all grouped under the `/puppet` API.
33
-
Other tools can access these services and use the OpenVox Servers's data for other purposes.
33
+
Other tools can access these services and use the OpenVox Server's data for other purposes.
34
34
35
35
The V3 API contains endpoints of two types: those that are based on dispatching to OpenVox's internal "indirector" framework, and those that are not (namely the [environments endpoint](#environments-endpoint)).
36
36
@@ -44,52 +44,47 @@ Using this API requires significant understanding of how OpenVox's internal serv
44
44
45
45
### Configuration management services
46
46
47
-
The OpenVox agent application directly uses these servcies to manage the configuration of a node.
47
+
The OpenVox agent application directly uses these services to manage the configuration of a node.
48
48
49
49
These endpoints accept payload formats formatted as JSON by default (MIME type of `application/json`), except for `File Content` and `File Bucket File`, which always use `application/octet-stream`.
50
50
51
51
> **Note:** Legacy PSON (MIME type of `text/pson`) is still an available format, but should be used only as a fallback for binary content.
OpenVox Server adds several unique endpoints of its own. They include these additional `/puppet/v3/` endpoints:
80
75
81
-
-[Environment classes](./puppet-api/v3/environment_classes.html), at `/puppet/v3/environment_classes`
82
-
-[Environment modules](./puppet-api/v3/environment_modules.html), at `/puppet/v3/environment_modules`
83
-
-[Static file content](./puppet-api/v3/static_file_content.html), at `/puppet/v3/static_file_content`
76
+
-[Environment classes](puppet-api/v3/environment_classes.html), at `/puppet/v3/environment_classes`
77
+
-[Environment modules](puppet-api/v3/environment_modules.html), at `/puppet/v3/environment_modules`
78
+
-[Static file content](puppet-api/v3/static_file_content.html), at `/puppet/v3/static_file_content`
84
79
85
80
It also includes these unique APIs, with endpoints containing other URL prefixes:
86
81
87
-
-[Status API](./status-api/v1/services.html), at `/status/v1/services`
88
-
-[Metrics v1 (mbeans) API](./metrics-api/v1/metrics_api.html), at `/metrics/v1/mbeans`
89
-
-[Metrics v2 (Jolokia) API](./metrics-api/v2/metrics_api.html), at `/metrics/v2/`
82
+
-[Status API](status-api/v1/services.html), at `/status/v1/services`
83
+
-[Metrics v1 (mbeans) API](metrics-api/v1/metrics_api.html), at `/metrics/v1/mbeans`
84
+
-[Metrics v2 (Jolokia) API](metrics-api/v2/metrics_api.html), at `/metrics/v2/`
90
85
- Admin API, at `/puppet-admin-api/v1/`:
91
-
-[Environment cache](./admin-api/v1/environment-cache.html), at `/puppet-admin-api/v1/environment-cache`
92
-
-[JRuby pool](./admin-api/v1/jruby-pool.html), at `/puppet-admin-api/v1/jruby-pool`
86
+
-[Environment cache](admin-api/v1/environment-cache.html), at `/puppet-admin-api/v1/environment-cache`
87
+
-[JRuby pool](admin-api/v1/jruby-pool.html), at `/puppet-admin-api/v1/jruby-pool`
93
88
94
89
### Error responses
95
90
@@ -109,7 +104,7 @@ Except for HEAD requests, error responses contain a body of a uniform JSON objec
109
104
-`message`: (`String`) A human-readable message explaining the error.
110
105
-`issue_kind`: (`String`) A unique label to identify the error class.
111
106
112
-
OpenVOx provides a [JSON schema for error objects](/openvox/latest/schemas/error.json). Endpoints implemented by OpenVox Server have a different error schema:
107
+
OpenVox provides a [JSON schema for error objects](/openvox/latest/schemas/error.json). Endpoints implemented by OpenVox Server have a different error schema:
113
108
114
109
```json
115
110
{
@@ -136,18 +131,22 @@ The following documents specify what is available and how to interact with it.
136
131
137
132
### SSL certificate-related services
138
133
139
-
These endpoints accept only plain-text payload formats. Historically, OpenVox has used the MIME type `s` to mean `text/plain`. In now uses `text/plain`, but continues to accept `s` as an equivalent.
134
+
These endpoints accept only plain-text payload formats. Historically, OpenVox has used the MIME type `s` to mean `text/plain`. It now uses `text/plain`, but continues to accept `s` as an equivalent.
0 commit comments