Full metadata for a service
Lists all information about a secondary web service.
Response
Details of the created service
A per-back-end unique identifier of the secondary web service, generated by the back-end during creation. MUST match the specified pattern.
A short description to easily distinguish entities.
Detailed multi-line description to explain the entity.
CommonMark 0.29 syntax MAY be used for rich text representation.
URL at which the secondary web service is accessible. Does not necessarily need to be located within the API.
Definition of the service type to access result data. All available service types can be retrieved via GET /service_types. Service types MUST be accepted in a case insensitive manner.
Describes whether a secondary web service is responding to requests (true) or not (false). Disabled services do not produce any costs.
Map of configuration settings, i.e. the setting names supported by the secondary web service combined with actual values. See GET /service_types for supported configuration settings. For example, this could specify the required version of the service, visualization details or any other service dependent configuration.
Additional attributes of the secondary web service, e.g. available layers for a WMS instance based on the bands in the underlying GeoTiff.
Date and time of creation (for batch jobs: the status 'created' was set), formatted as a RFC 3339 date-time.
The billing plan to process and charge the job or service with.
Billing plans MUST be handled in a case insensitive manner.
The plans can be retrieved from GET /, but the value returned here may not be in the list of plans any longer.
An amount of money or credits. The value MUST be specified in the currency the back-end is working with. The currency can be retrieved by calling GET /. If no currency is set, this field MUST be null.
Maximum amount of costs the request is allowed to produce. The value MUST be specified in the currency of the back-end. No limits apply, if the value is null or the back-end has no currency set in GET /.
The minimum severity level for log entries that the back-end stores for the processing request.
The order of the levels is as follows (from low to high severity): debug, info, warning, error. That means if warning is set, the back-end will only store log entries with the level warning and error.
The default minimum log level is info. Users need to specifically set this property to debug to capture all log entries. It is RECOMMENDED that users set the level at least to "warning" in production workflows.