Changelog

Summary

• Added kind property to ApiToken and CreateApiTokenRequest schemas, allowing specification of token type.
• Introduced new permissions for various API endpoints related to API tokens and user roles.
• Modified query parameters for the /organizations/{organizationId}/tokens endpoint, including changes to pagination and sorting criteria.

Added

• Schemas

  • ApiToken
    • kind: Specifies the type of API token. Options are STANDARD and DIRECT_ACCESS.
  • CreateApiTokenRequest
    • kind: Specifies the type of API token, defaulting to STANDARD.

• Permissions

  • /organizations/{organizationId}/tokens
    • GET, POST: Requires organization.apiTokens.access.
  • /organizations/{organizationId}/tokens/{tokenId}
    • GET, POST, DELETE: Requires organization.apiTokens.access.
  • /organizations/{organizationId}/tokens/{tokenId}/roles
    • POST: Requires organization.apiTokens.access.
  • /organizations/{organizationId}/tokens/{tokenId}/rotate
    • POST: Requires organization.apiTokens.access.
  • /organizations/{organizationId}/users/{userId}/roles
    • POST: Requires organization.userRoles.access.

• Query Parameters

  • /organizations/{organizationId}/tokens
    • sorts: Sorting criteria for API tokens, with options like name:asc, createdAt:desc, etc.

Changed

• Schemas

  • ApiToken
    • kind is now a required property.

• Query Parameters

  • /organizations/{organizationId}/tokens
    • kind: Replaced offset parameter. Now specifies the type of API token to list.
    • offset: Previously limit, now specifies pagination offset.
    • limit: Previously sorts, now specifies pagination limit with a default of 20 and a maximum of 1000.

• Parameter Descriptions

  • Updated descriptions for kind, offset, and limit parameters to reflect their new purposes.