---
title: "Discussion on \"Stop using `any` — here's how to type your messy API responses correctly\" | Hashnode"
description: "Discussion on \"Stop using `any` — here's how to type your messy API responses correctly\". TypeScript isn’t the problem your any is. If you're using any, you're hiding bugs — not fixing them. TypeScript can’t save you if you lie to it."
url: "https://hashnode.com/posts/stop-using-any-here-s-how-to-type-your-messy-api-responses-correctly/69d33c4c40c9cabf449e342a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop using \`any\` — here's how to type your messy API responses correctly](https://stackdevlife.hashnode.dev/stop-using-any-here-s-how-to-type-your-messy-api-responses-correctly?utm_source=hashnode&utm_medium=feed)

TypeScript isn’t the problem your any is. If you're using any, you're hiding bugs — not fixing them. TypeScript can’t save you if you lie to it.

Apr 6 · 12 min read · stackdevlife.hashnode.dev  
Read the article

-   [#typescript](https://hashnode.com/tag/typescript)
-   [#zod](https://hashnode.com/tag/zod)
-   [#frontend](https://hashnode.com/tag/frontend)
-   [#api](https://hashnode.com/tag/api)
-   [#typesafety](https://hashnode.com/tag/typesafety)

## Written by

[sandeepbansod007](https://hashnode.com/@sandeepbansod)

@sandeepbansod · Nagpur, India

  
[View profile](https://hashnode.com/@sandeepbansod)

Helping developers think, build, and grow

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
