When multiple teams across different domains and languages build APIs, it’s only a matter of time before standards diverge—different naming conventions, different ways of working, and different approaches to security. Everyone has the best intentions, but without guardrails, consistency and quality quickly slip, especially as standards evolve over time!

So how do we prevent this? How can we set up lightweight checks that integrate with the tools we already use, without forcing massive changes across every codebase before we can even get started?

In this session, we’ll explore how Spectral, a linting tool for OpenAPI, helps you bring order to your API definitions by enforcing style, consistency, and security rules. We’ll cover:

- A (re)introduction to OpenAPI
- Getting started with Spectral
- Creating custom rulesets tailored to your organization
- Running validations in CI/CD pipelines to catch issues early
- Applying well-known community rulesets to align with best practices
- Strengthening API security through automated checks

You’ll walk away with practical tools and patterns to keep your API definitions clean, consistent, and secure, no matter how many teams are involved!