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

Tower Teams API

The Teams API from Tower — 6 operation(s) for teams.

Tower Teams API is one of 27 APIs that Tower 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 13 operations across 6 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version v0.11.16.

Requests are made against a single base URL, https://api.tower.dev/v1.

13 operations 6 paths 29 schemas 3 DELETE4 GET4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0.11.16
Base URL
https://api.tower.dev/v1
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Tower Teams API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (APIKeyAuth). It accepts HTTP bearer tokens (AccessTokenAuth).

  • APIKeyAuth — API key created by a Tower user or Tower service account to authenticate an API request.
  • AccessTokenAuth — Access token authentication scheme which uses an access token provided by the Tower API as part of a Tower session (see documentation about creating sessions).

Paths & Operations 13

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

Teams 13
DELETE
/teams
Delete team
delete-team body → 200default
GET
/teams
List teams
list-teams 2 params → 200default
POST
/teams
Create team
create-team body → 200default
GET
/teams/{name}
Describe team
describe-team 1 param → 200default
PUT
/teams/{name}
Update team
update-team 1 param body → 200default
DELETE
/teams/{name}/invites
Delete team invitation
delete-team-invitation 1 param body → 200default
GET
/teams/{name}/invites
List team invitations
list-team-invitations 1 param → 200default
POST
/teams/{name}/invites
Invite team member
invite-team-member 1 param body → 200default
POST
/teams/{name}/invites/resend
Resend team invitation
resend-team-invitation 1 param body → 200default
POST
/teams/{name}/leave
Leave team
leave-team 1 param → 200default
DELETE
/teams/{name}/members
Remove team member
remove-team-member 1 param body → 200default
GET
/teams/{name}/members
List team members
list-team-members 1 param → 200default
PUT
/teams/{name}/members
Update team member
update-team-member 1 param body → 200default

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are User (12 properties), ErrorModel (7 properties), Team (6 properties), Pagination (4 properties). Each schema is shown below with its type and property counts.

UpdateTeamResponse
object
2 properties 1 required
Token
object
3 properties 2 required
DescribeTeamResponse
object
4 properties 3 required
RemoveTeamMemberParams
object
2 properties 1 required
Team
object
6 properties 4 required
UpdateTeamMemberParams
object
3 properties 1 required
ResendTeamInvitationResponse
object
2 properties 1 required
ListTeamMembersResponse
object
2 properties 1 required
User
object
12 properties 11 required
Pagination
object
4 properties 4 required
DeleteTeamInvitationParams
object
2 properties 1 required
ResendTeamInvitationParams
object
3 properties 1 required
TeamInvitation
object
4 properties 4 required
LeaveTeamResponse
object
2 properties 1 required
InviteTeamMemberParams
object
4 properties 2 required
TeamMembership
object
3 properties 3 required
RemoveTeamMemberResponse
object
2 properties 1 required
DeleteTeamResponse
object
2 properties 1 required
DeleteTeamInvitationResponse
object
2 properties 1 required
ErrorModel
object
7 properties
ErrorDetail
object
3 properties
CreateTeamResponse
object
2 properties 1 required
InviteTeamMemberResponse
object
2 properties 1 required
ListTeamsResponse
object
3 properties 2 required
DeleteTeamParams
object
2 properties 1 required
ListTeamInvitationsResponse
object
2 properties 1 required
UpdateTeamMemberResponse
object
2 properties 1 required
CreateTeamParams
object
2 properties 1 required
UpdateTeamParams
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tower-teams-api-openapi.yml Raw ↑

Other APIs Tower publishes across the network.

Tower Accounts API
Tower Alerts API
Tower Api Keys API
Tower Apps API
Tower Catalogs API
Tower Environments API
Tower Feature Flags API
Tower Guests API
Tower Login API
Tower Organizations API
Tower Plan API
Tower Runners API
Where this information came from

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