How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Solo.io API Keys API

API key management endpoints

Solo.io API Keys API is one of 15 APIs that Solo.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include APIKeys. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, /v1.

4 operations 3 paths 4 schemas 2 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://portal.example.com/v1
Authentication
HTTP Bearer, API Key, API Key
Resource Areas
1

Authentication & Security 3

Solo.io API Keys API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the cookie as id_token (identityToken). An API key is passed in the cookie as access_token (accessToken).

  • bearerAuth — Bearer token passed in the Authorization header
  • identityToken — idtoken cookie set by the identity provider after OIDC login
  • accessToken — accesstoken cookie set by the identity provider after OIDC login

Paths & Operations 4

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

api-keys 4

API key management endpoints

GET
/apps/{appID}/api-keys
List app API keys
ListAppApiKeys 1 param → 200401404500
POST
/apps/{appID}/api-keys
Create app API key
CreateAppApiKey 1 param body → 201400401404409500
DELETE
/apps/{appID}/api-keys/{keyID}
Delete app API key
DeleteAppApiKey 2 params → 204401500
DELETE
/api-keys/{keyID}
Delete API key
DeleteApiKey 1 param → 204401500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are BaseEntity (3 properties), CreateApiKeyRequest (2 properties). Each schema is shown below with its type and property counts.

BaseEntity
object
Base entity with common fields
3 properties 2 required
ApiKey
API key information (without the actual key value)
ApiKeyWithSecret
API key with the actual key value (only returned at creation time)
CreateApiKeyRequest
object
Request body for creating an API key
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

solo-io-api-keys-api-openapi.yml Raw ↑

Other APIs Solo.io publishes across the network.

Solo.io API Products API
Solo.io AP Is API
Solo.io Applications API
Solo.io Apps API
Solo.io Auth API
Solo.io Health API
Solo.io Me API
Solo.io Metadata API
Solo.io OAUTH Credentials API
Solo.io Subscriptions API
Solo.io Teams API
Solo.io User API
Where this information came from

This is an independent, third-party profile of Solo.io API Keys API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.