# Fingerprint b64 not URL-friendly on pipelines

**URL:** https://discuss.elastic.co/t/fingerprint-b64-not-url-friendly-on-pipelines/381515
**Category:** Elasticsearch
**Created:** [September 2, 2025, 10:48am UTC](https://discuss.elastic.co/t/fingerprint-b64-not-url-friendly-on-pipelines/381515 "2025-09-02T10:48:31Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Victor\_Monteagudo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/victor_monteagudo/32/141512_2.png) [@Victor\_Monteagudo](https://discuss.elastic.co/u/Victor_Monteagudo)
#### Post date: [September 2, 2025, 10:48am UTC](https://discuss.elastic.co/t/fingerprint-b64-not-url-friendly-on-pipelines/381515/1 "2025-09-02T10:48:31Z")

</div>

Hello!

In our ingestion pipeline, we use a field fingerprint as an ID. This ID is used in API paths for searches, such as /host/{id}.

We are having problems with B64 due to Elastic transforming the fingerprint to B64 before saving it.

Is there any possibility of changing this to BASE64-URL-friendly or HEX?

Thank you.