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 Teams API

Team management endpoints

Solo.io Teams 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 Team. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against 2 base URLs: /v1, http://portal.example.com/v1.

18 operations 9 paths 20 schemas 4 DELETE7 GET5 POST2 PUT

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 Teams 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 18

Across 9 paths, the API surfaces 18 operations — 4 DELETE, 7 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

teams 18

Team management endpoints

GET
/teams
List teams
ListTeams → 200401500
POST
/teams
Create team
CreateTeam body → 201400401409500
GET
/teams/{teamID}
Get team details
GetTeam 1 param → 200401404500
PUT
/teams/{teamID}
Update team
UpdateTeam 1 param body → 200400401500
DELETE
/teams/{teamID}
Delete team
DeleteTeam 1 param → 204401409500
GET
/teams/{teamID}/apps
List team apps
ListTeamApps 1 param → 200401500
POST
/teams/{teamID}/apps
Create team app
CreateTeamApp 1 param body → 201400401409500
GET
/teams/{teamID}/members
List team members
ListTeamMembers 1 param → 200401500
POST
/teams/{teamID}/members
Add team member
AddTeamMember 1 param body → 201400401404409500
DELETE
/teams/{teamID}/members/{memberID}
Remove team member
RemoveTeamMember 2 params → 204401500
DELETE
/teams/{teamId}
Deletes a team
DeleteTeam 1 param → 204400401403404500
GET
/teams/{teamId}
Gets a team
GetTeamById 1 param → 200401403404500
PUT
/teams/{teamId}
Updates a team
UpdateTeam 1 param body → 200400401403404500
GET
/teams/{teamId}/apps
Lists all team apps
ListTeamApplications 1 param → 200401403404500
POST
/teams/{teamId}/apps
Creates an application
CreateTeamApplication 1 param body → 201400401403404409500
GET
/teams/{teamId}/members
List of team users
ListTeamMembers 1 param → 200401404500
POST
/teams/{teamId}/members
Adds a member to a team
AddTeamMember 1 param body → 201400401403404500
DELETE
/teams/{teamId}/members/{userId}
Removes a member from a team
RemoveTeamMember 2 params → 204401403404500

Schemas 20

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

CreateAppRequest
object
Request body for creating an application
2 properties 1 required
ApplicationCreate
object
Create
2 properties 1 required
BaseEntity
object
Base entity with common fields
3 properties 2 required
UpdateTeamRequest
object
Request body for updating a team
2 properties
TeamSummary
Team summary information
RateLimit
object
Rate limit configuration
2 properties 2 required
RateLimit_2
object
2 properties
TeamDetails
Team details including member list
BaseEntity_2
object
4 properties
TeamCreate
object
Create a new team
2 properties 1 required
TeamUpdate
CreateTeamRequest
object
Request body for creating a team
2 properties 1 required
ApplicationMetadata
User
TeamMember
Team member information
AddTeamMemberRequest
object
Request body for adding a team member (either userId or email required)
2 properties
Team
App
Application information
Application
ResourceMetadata
object
Metadata attached to a resource (app or subscription) including rate limits and custom key-value pairs
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Solo.io publishes across the network.

Solo.io API Keys API
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 User API
Where this information came from

This is an independent, third-party profile of Solo.io Teams 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.