Policy Troubleshooter API
v1
Policy Troubleshooter API
v1beta
MiW User Result REST API
0.1.0
[UPM] MiW User REST API operations
MiW User Result REST API
0.1.0
[UPM] MiW User REST API operations
KV Store API
v1beta1.2
With the Splunk Cloud KV store service in Splunk Cloud Services, you can save and retrieve data within your Splunk Cloud apps, enabling you to manage and maintain state in your application.
KV Store API
v1beta1.2
With the Splunk Cloud KV store service in Splunk Cloud Services, you can save and retrieve data within your Splunk Cloud apps, enabling you to manage and maintain state in your application.
Cloud Asset API
v1p1beta1
The cloud asset API manages the history and inventory of cloud resources.
FORTNITE
3.1.5
REST API about Fortnite game
Remote Diagnostic Support
1.0
The Remote Diagnostic Support API will provide the possibility for 3rd party applications (e.g. ADAC, ATU, etc.) to access vehicle diagnostics data remotely on behalf of the Daimler customer. To use the endpoints you need a valid vin/fin (vehicleId).
Policy Troubleshooter
v1beta
Policy Troubleshooter
v1beta
Unstable internal _ui API for Red Hat Automation Hub
0.1.0
# Introduction **NOTE: This is not a stable API and should not be relied upon.** This is the <a href="https://www.openapis.org">OpenAPI</a> specification for the **Red Hat Ansible Automation Hub** _ui API. ## OpenAPI Information <a target="_top" href="https://swagger.io/docs/specification/about/">Swagger.io OpenAPI documentation</a> <a target="_top" href="https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md">OpenAPI Specification</a> <a target="_top" href="https://github.com/ansible/galaxy-api/blob/master/openapi/openapi.yaml">Download the Automation Hub OpenAPI Specification</a>. # API Conventions ## Pagination Resource lists are always paginated. This pagination format is based on the <a href="https://jsonapi.org/format/#document-structure">JSON API document structure.</a> The response will look similar to this: ```json { "meta": { "count": 5 }, "links": { "first": "/namespaces/?offset=0&limit=1", "last": "/namespaces/?offset=7&limit=1", "next": "/namespaces/?offset=5&limit=1", "previous": "/namespaces/?offset=3&limit=1" }, "data": [ { "name": "my_namespace" } ] } ``` ## Errors Error responses always have a top level object with an 'errors' field. The value of the 'errors' field is a list of Error objects. Example `Errors` response for a 404 on `GET /unicorn/11` ```json { "errors": [ { "code": "not_found", "detail": "Record /unicorn/11 was not found", "title": "Record not found.", "status": "404", "source": { "parameter": "string", "pointer": "string" } } ] } ```