# Get data api has old table names

**URL:** <https://forum.bubble.io/t/get-data-api-has-old-table-names/20014>\
**Category:** Database\
**Created:** [November 4, 2017, 2:18am UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014 "2017-11-04T02:18:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![blueback09](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/blueback09/32/7122_2.png) [@blueback09](https://forum.bubble.io/u/blueback09)\
**Post date:** [November 4, 2017, 2:18am UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014/1 "2017-11-04T02:18:04Z")

</div>

I’m building scripts to convert the json I receive from the GET data API into data in a mysql database on another server.

In most cases I can identify the data with the “\_type” field because it has this pattern  
“user” for built-in tables  
“custom.whatever\_something” for tables I created

However, as I’m going through the data one of the data sets has the wrong name in the “\_type” field. Where I’m expecting “custom.preset\_array” it says “custom.metric\_array1”.

Maybe I changed the name of the table from metric\_array1 to preset\_array at some point? I don’t remember.

At any rate, I want to be able to trust the API to tell me what the data is CURRENTLY called. I don’t even see a way to look up what the table names used to be.

Is this a mistake? Should the GET data API return the current name of the table instead of an old name? @emmanuel

---

<div class="post-metadata">

**Author:** ![djwideman](https://avatars.discourse-cdn.com/v4/letter/d/9fc348/32.png) [@djwideman](https://forum.bubble.io/u/djwideman)\
**Post date:** [November 4, 2017, 9:34am UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014/2 "2017-11-04T09:34:55Z")

</div>

I’m sure you thought of this already, but I ran into similar problem and it was because I hadn’t deployed. If you change an endpoint (name, properties, etc.), external servers calling in will get the old endpoint until you re-deploy.

---

<div class="post-metadata">

**Author:** ![blueback09](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/blueback09/32/7122_2.png) [@blueback09](https://forum.bubble.io/u/blueback09)\
**Post date:** [November 4, 2017, 4:11pm UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014/3 "2017-11-04T16:11:08Z")

</div>

Yeah, I’ve deployed a lot since that table name must have been changed.

---

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/philip/32/17830_2.png) [@philip](https://forum.bubble.io/u/philip)\
**Post date:** [November 4, 2017, 6:12pm UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014/4 "2017-11-04T18:12:25Z")

</div>

Could this be related to the toggle option in Settings → API → Use field display instead of ID for key names?

![e472cd8a6a3d4e9a670d28060f1bafe0](https://us1.discourse-cdn.com/bubble/original/3X/0/1/0144f796bae8978132a674d8b9908ff2c7b1b76e.png)

> **[Introduction](https://manual.bubble.io/)**
>
> Welcome to the Bubble Docs.

---

<div class="post-metadata">

**Author:** ![blueback09](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/blueback09/32/7122_2.png) [@blueback09](https://forum.bubble.io/u/blueback09)\
**Post date:** [November 4, 2017, 7:56pm UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014/5 "2017-11-04T19:56:04Z")

</div>

Probably a similar idea, but I think that refers to the field names, not the table names, and I’ve already got it checked anyway.

---

<div class="post-metadata">

**Author:** ![emmanuel](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/emmanuel/32/27657_2.png) [@emmanuel](https://forum.bubble.io/u/emmanuel)\
**Post date:** [November 4, 2017, 8:35pm UTC](https://forum.bubble.io/t/get-data-api-has-old-table-names/20014/6 "2017-11-04T20:35:23Z")

</div>

We currently don’t update the type field indeed and show the raw type ID. We’ll look into fixing this but it’s not a quick one as it could break existing apps.
