---
title: "Creating a Development  App from a Production App"
url: "https://help.tabidoo.cloud/en/article/creating-a-development-app-from-a-production-app"
language: "en"
last_updated: "2026-06-16T13:43:26.506Z"
---

# Creating a Development  App from a Production App

### Overview

Sometimes, you begin development directly in a single application — without a separate DEV environment. The app may already be filled with data and actively used by customers. If you later need to separate development from production, you can now use a new API function that allows you to create a DEV app from an existing production app.

This feature is useful when you want to:

-   test new functionality independently,
-   implement a proper development cycle (DEV → PROD),
-   avoid overwriting the current app or changing templates.

* * *

### API Call

```plaintext
POST https://app.tabidoo.cloud/api/v2/templates/createDevAppFromProdApp
```

#### Request Body

```plaintext
{
  "applicationId": "abc12345-048e-4ada-ae48-2ffd531cdcdc"
}
```

⚠️ **Important**:

-   You must insert the **real application ID** into `applicationId`.
-   The ID can be obtained using **F12 → Console → Network** in the browser.
-   `internalName` or `niceName` cannot be used here.

  
Use this version when the app is a standalone production app and has not been created from a template, and does not yet have a DEV linked to it.

* * *

### 🔐 Authorization

To perform authenticated API calls in Tabidoo, you must use a **Bearer token**. This token ensures secure access and must follow specific rules to work correctly.

**CRITICAL – Token Ownership**

**DO NOT use shared tokens or tokens taken from the web app (e.g. via Developer Tools).**

-   These tokens **will NOT work** and API requests will fail.

**The API token MUST be created under the application owner account.**

-   Tokens from other users (even with access to the app) **are not valid**.

Each user can generate their own API token in their personal settings.

> You can find the relevant settings under **User Profile → API**, or follow this guide:  
> [API Token Setup Help Article](https://help.tabidoo.cloud/en/article/api)

* * *

### How to Authorize

When using tools like **Postman**, or when sending HTTP requests programmatically (e.g., with `fetch` or `axios`), you must set the `Authorization` header as follows:

```plaintext
Authorization: Bearer your-api-token 
```

Make sure to:

-   Copy the **entire token** string without any modifications.
-   Do not shorten or alter the token.
-   Use it **exactly** as shown above — including the `Bearer` prefix.

* * *

### What Gets Copied to the New DEV App

Only technical components are copied:

`Workflow`

`ScriptExtension`

`Reports`

`CustomDataSource`

`Roles`

#### **Regular user data is not transferred!**  
  
Where to Find the New DEV App

After the DEV app is created, you can find it listed under your **Private Templates** in Tabidoo.

* * *

### Special Cases

#### 1\. App was originally downloaded from a template

If the application you're working with was originally created from a template, the API call will return an error to prevent accidental linking of multiple DEV applications to one template. In this case, you must force the creation of a new DEV and reassign the template dependency.

Use this format:

```plaintext
{
  "applicationId": "abc12345-048e-4ada-ae48-2ffd531cdcdc",
  "overrideExistingTemplateId": "12345678-1234-4123-1234-123456789123"
}
```

#### 2\. App already has a DEV created

If a DEV version has already been created for this application, any further call to create another DEV will also fail — unless forced explicitly with the `overrideExistingTemplateId` parameter, as shown above.

* * *

### 💡 Example Use Case

> The application **CRM1** is already in production use. I want to create a development version **CRM1 DEV** where I can test new changes. I don't want to switch templates or adjust dependencies manually. Using this API, I can easily create a new DEV version.