Do I need to generate SDKs from my API spec too?

Not necessarily.

It depends on who consumes your API and how much client support you want to provide.

You usually should generate SDKs if:

• You have multiple client teams/languages to support
• Your API is public or widely used
• You want to reduce client integration errors
• You want a consistent, typed, versioned way to call the API

You may not need SDKs if:

• The API is used by only a few internal teams
• Consumers are happy calling the raw HTTP API directly
• You want to avoid the maintenance burden of keeping SDKs in sync
• Your API is simple enough that docs + examples are sufficient

Common approach

Many teams start with:

1. API spec
2. Great docs + examples
3. Optional generated SDKs for the most important languages

That gives you a good balance without overcommitting.

Watch out

If you generate SDKs, you’re signing up to:

• keep them versioned with the API
• publish them reliably
• test them against the spec
• handle breaking changes carefully

So: generate SDKs if they materially help your users; otherwise, don’t make them a requirement.

If you want, I can also give you a decision checklist for whether SDK generation is worth it for your API.