Humanitec ResourceDefinition API
A Resource Definitions describes how and when a resource should be provisioned. It links a driver (the how) along with a Matching Criteria (the when) to a Resource Type. This allows Humanitec to invoke a particular driver for the required Resource Type in the context of a particular Application and Environment.The schema for the `driver_inputs` is defined by the `input_schema` property on the DriverDefinition identified by the `driver_type` property.
Humanitec ResourceDefinition API is one of 45 APIs that Humanitec publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include ResourceDefinition. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and authentication docs.
This API exposes 10 operations across 5 paths, and defines 13 schemas. It is described by OpenAPI 3.0.0, at version 0.28.24.
Requests are made against a single base URL, https://api.humanitec.io/.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 10
Across 5 paths, the API surfaces 10 operations — 2 DELETE, 3 GET, 1 PATCH, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
A Resource Definitions describes how and when a resource should be provisioned. It links a driver (the how) along with a Matching Criteria (the when) to a Resource Type. This allo…
Schemas 13
The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ActiveResourceResponse (20 properties), ResourceDefinitionResponse (16 properties), CreateResourceDefinitionRequestRequest (8 properties), MatchingCriteriaResponse (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Humanitec 12
Other APIs Humanitec publishes across the network.