Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

IronCore Labs Configuration Assignment API

Assignments between KMS configurations and tenants

IronCore Labs Configuration Assignment API is one of 5 APIs that IronCore Labs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Configuration Assignment. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 6 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 3.1.0.

Requests are made against a single base URL, http://localhost:3000/api.

6 operations 3 paths 6 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.1.0
Base URL
https://ironcorelabs.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

IronCore Labs Configuration Assignment API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization). By default, every request must be authenticated.

  • Authorization — VAB authorization header. Form: vab:1:

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Configuration Assignment 6

Assignments between KMS configurations and tenants

GET
/1/tenants/{tenantId}/assignments
Tenant KMS Assignment List
get-tenants-tenantId-assignments 8 params → 200401
GET
/1/kms/configs/{kmsConfigId}/assignments
Configuration Assignment List
get-kms-configs-kmsConfigId-assignments 8 params → 200401
GET
/1/kms/configs/{kmsConfigId}/tenants/{tenantId}
KMS Assignment Get
get-kms-configs-kmsConfigId-tenants-tenantId 3 params → 200400401
POST
/1/kms/configs/{kmsConfigId}/tenants/{tenantId}
KMS Assignment Create
post-kms-configs-kmsConfigId-tenants-tenantId 3 params → 200400401
PUT
/1/kms/configs/{kmsConfigId}/tenants/{tenantId}
KMS Assignment Update
put-kms-configs-kmsConfigId-tenants-tenantId 3 params body → 200400401
DELETE
/1/kms/configs/{kmsConfigId}/tenants/{tenantId}
KMS Assignment Delete
delete-kms-configs-kmsConfigId-tenants-tenantId 3 params → 200400401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are KmsConfigAssignmentResponse (7 properties), CreatedBy (3 properties). Each schema is shown below with its type and property counts.

KmsConfigId
integer
KMS configuration ID
CreatedByType
string
Creator type
Timestamp
string
RFC3339 timestamp
TenantId
string
Tenant ID
CreatedBy
object
Metadata about creating user/service
3 properties 3 required
KmsConfigAssignmentResponse
object
7 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ironcore-labs-configuration-assignment-api-openapi.yml Raw ↑

Other APIs IronCore Labs publishes across the network.

IronCore Labs KMS Configuration API
IronCore Labs Tag API
IronCore Labs Tenant API
IronCore Labs Tenant Secret API