---
title: "Discussion on \"Your API Is Leaking Source Fingerprints. Here's How to Stop It.\" | Hashnode"
description: "Discussion on \"Your API Is Leaking Source Fingerprints. Here's How to Stop It.\". Why transformed data still reveals where it came from"
url: "https://hashnode.com/posts/your-api-is-leaking-source-fingerprints/69c28b6092029d915f263e07"
---

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

Discussion

# [Your API Is Leaking Source Fingerprints. Here's How to Stop It.](https://blog.tripvento.com/your-api-is-leaking-source-fingerprints?utm_source=hashnode&utm_medium=feed)

Why transformed data still reveals where it came from

Mar 24 · 8 min read · blog.tripvento.com  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#python](https://hashnode.com/tag/python)
-   [#buildinpublic](https://hashnode.com/tag/buildinpublic)
-   [#api](https://hashnode.com/tag/api)
-   [#api-fingerprinting](https://hashnode.com/tag/api-fingerprinting)

## Written by

[Ioan Istrate](https://hashnode.com/@tripvento)

@tripvento · Washington D.C.

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

Context aware hotel rankings powered by geospatial intelligence and semantic AI.

Building Tripvento, a B2B travel API that matches hotels to traveler intent using PostGIS, semantic AI, and 14 traveler personas. Previously worked on ranking systems at U.S. News &amp; World Report. Head TA at Georgia Tech's Graduate Intro to OS course. Writing about geospatial engineering, Django at scale, and building travel tech infrastructure.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
