# \[F\] json API "catch" missing tag

**URL:** https://community.mp3tag.de/t/f-json-api-catch-missing-tag/16166
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [September 21, 2014, 8:58pm UTC](https://community.mp3tag.de/t/f-json-api-catch-missing-tag/16166 "2014-09-21T20:58:23Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![vkostas](https://community.mp3tag.de/user_avatar/community.mp3tag.de/vkostas/32/227_2.png) [@vkostas](https://community.mp3tag.de/u/vkostas)
#### Post date: [September 22, 2014, 4:19pm UTC](https://community.mp3tag.de/t/f-json-api-catch-missing-tag/16166/4 "2014-09-22T16:19:47Z")

</div>

> [@Florian](#):
>
> Hi Victor,
> 
> thanks for your feedback! Glad you like the new JSON-related functions 🙂
> 
> Kind regards  
> Florian

I noticed something else (I found a workaround) which is "caused" by the **URL-UTF-8** encoding.  
API fails when using complex search (multiple parameters on the placeholder **%s** ). That's because **URL-UTF-8** encodes the ampersand character (&).  
I replaced encoding with **UTF-8** and complex search is back to life again.

Please consider some websript suggestions ([**in this new topic**](https://community.mp3tag.de/t/16169/1)).  
Please strogly consider point 4. I just realized we will lose "Advanced scripting" tricks by using json.  
Using "traditional" scripting we were collecting information on the selected API stream (use regexp, etc) and storing it to temporary tags, e.g. scan all tracks to find total number of discs to make it available to all tracks (in a new tracks loop).

---

_[View the full topic](https://community.mp3tag.de/t/f-json-api-catch-missing-tag/16166)._