Get spoke system registration information
get
/status/routing/apis
Request
Query Parameters
-
ids(required): array[string]
The list of ids for which spoke system registration is to be checked. Each value in the list of values should in the format of <api-id>:<api-version>:<path-id>. All three parameters are mandatory and should be non empty values. Incase of mising values or extra values or empty values ,**400 Bad request** will be returned.
There's no request body for this operation.
Back to TopResponse
Supported Media Types
- application/json
200 Response
Routing Status is TRUE, fabric will be able to route the request with the given combination of api-id, version-id and path-id
Root Schema : Results
Type:
Show Source
array
Example:
[
{
"api-id":"tmf-632",
"api-version":"v4",
"path-id":"individual",
"served":true
},
{
"api-id":"tmf-632",
"api-version":"v4",
"path-id":"organization",
"served":false
}
]
Nested Schema : Result
Type:
Show Source
object
-
api-id(required): string
-
api-version(required): string
-
path-id(required): string
-
served(required): boolean
Indicates whether fabric will be able to route the request with the given combination of api-id, version-id, and path-id or not.
400 Response
Bad Request
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
401 Response
Unauthorized
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
500 Response
Internal Server Error
Root Schema : Error
Type:
object
Used when an API throws an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx)
Show Source
-
@baseType: string
When sub-classing, this defines the super-class.
-
@schemaLocation: string
(uri)
A URI to a JSON-Schema file that defines additional attributes and relationships
-
@type: string
When sub-classing, this defines the sub-class entity name.
-
code(required): string
Application relevant detail, defined in the API or a common list.
-
message: string
More details and corrective actions related to the error which can be shown to a client user.
-
reason(required): string
Explanation of the reason for the error which can be shown to a client user.
-
referenceError: string
(uri)
URI of documentation describing the error.
-
status: string
HTTP Error code extension
Examples
The following example shows how to get spoke system registration information for a specific api, version and path by submitting a get request on the REST resource using cURL.
cURL Command
curl --<username:password> --request GET
'{FABRIC_HOST}/status/routing/apis?id={api-id}:{version-id}:{path-id}' --header
Authorization: Bearer <accessToken> --header 'Content-Type: application/json'
Example of Response Body
The following shows an example of the response body in JSON format.
[ { "api-id":"tmf-632", "api-version":"v4", "path-id":"individual", "served":true }, { "api-id":"tmf-632", "api-version":"v4", "path-id":"organization", "served":false } ]