Increasing the SELECT APIs coverage

We are moving SELECT towards supporting a fully headless experience: everything you can do in the web app should also be available to you over the API, and soon over MCP.

The new v2 API is a big step. It is the same API the SELECT app itself runs on, so anything the product can query or configure, your scripts and pipelines can access too.

What you can now configure

• Connections, for every platform. Add, update, test and remove Snowflake accounts, BigQuery projects, Databricks connections, AWS payer accounts and Tableau sites, and read sync state for each. Credentials are write-only: a read tells you which authentication method and user a connection uses, never the secret.
• Budgets. Create and change spend thresholds over a recurring or fixed period, scope them to a team or a slice of spend, and read what each has spent against where it is heading.
• Insights. List and inspect the savings opportunities SELECT finds in your usage.
• Actions. Track savings resulting from optimizations, and query realized savings.
• Audit logs. Export your organization's activity record directly, instead of through the UI.
• Access management. Teams, members, users, roles, SSO group mappings, default role grants and invitations.
• Usage groups. Organize spend into the groups that matter to you.
• Ticket links. Connect issues in your ticketing system to insights or actions.

Coming soon

• Monitors. Define what SELECT watches and who it tells, so your alerting lives next to the rest of your configuration instead of in a UI.
• Dashboards. Create dashboards and the blocks on them, so a new team can be onboarded with the views they need already in place.
• Saved views and favorites. Carry the slices your team works from between environments, rather than rebuilding them by hand.
• Everything as MCP. Anything the API can do, your agent will be able to do too, through our MCP server.

Moving off v1

The v1 API under /api/... is now deprecated, and access will be removed on December 14th. Every v1 endpoint carries a note in the reference pointing at its v2 replacement, and what changed from v1 covers the shape changes: PATCH instead of PUT, cursor pagination on lists, and new identifiers for SSO groups, team members and user roles.

If you manage SELECT with Terraform, keep an eye out for a major version bump of our Terraform provider in the coming weeks, which points its resources at the v2 routes.