Create entity schema

This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.

Adds a new entity to the specified app.

This changes the app’s live data model, so it takes effect immediately. It doesn’t change the file that defines that model in the app’s source code. Since Base44 rebuilds the live model whenever the file is written or the app’s code is pulled from GitHub, a change made using this endpoint may be reverted.

To change the model for good, change the entities configuration files.

You can’t create User, which is built in. Use Update entity schema with User to add custom fields to it.

POST /api/apps/{app_id}/entity-schemas

Create entity schema

cURL

curl --request POST \
  --url https://app.base44.com/api/apps/{app_id}/entity-schemas \
  --header 'Content-Type: application/json' \
  --header 'api_key: <api-key>' \
  --data '
{
  "entity_name": "Invoice",
  "entity_schema": {
    "name": "Invoice",
    "properties": {
      "amount": {
        "description": "Total amount in cents",
        "type": "number"
      },
      "status": {
        "enum": [
          "draft",
          "sent",
          "paid"
        ],
        "type": "string"
      }
    },
    "required": [
      "amount"
    ],
    "rls": {
      "read": {
        "created_by": "{{user.email}}"
      }
    },
    "type": "object"
  }
}
'

200

{
  "entity_name": "Invoice",
  "entity_schema": {
    "name": "Invoice",
    "properties": {
      "amount": {
        "description": "Total amount in cents",
        "type": "number"
      },
      "status": {
        "enum": [
          "draft",
          "sent",
          "paid"
        ],
        "type": "string"
      }
    },
    "required": [
      "amount"
    ],
    "rls": {
      "read": {
        "created_by": "{{user.email}}"
      }
    },
    "type": "object"
  }
}

Authorizations

api_key · string · header · required

Personal API key.

Path Parameters

app_id · string · required

ID of the app whose entity schemas you want to work with.

Body

application/json

entity_name · string · required

Name for the new entity. Letters, numbers, and underscores only. Cannot be User.

Example:

"Invoice"

entity_schema · Entity Schema · object · required

The entity's JSON Schema. Needs "type": "object" and a properties object, plus any required fields and row-level security rules under rls.

Example:

{
  "name": "Invoice",
  "properties": {
    "amount": {
      "description": "Total amount in cents",
      "type": "number"
    },
    "status": {
      "enum": ["draft", "sent", "paid"],
      "type": "string"
    }
  },
  "required": ["amount"],
  "rls": {
    "read": { "created_by": "{{user.email}}" }
  },
  "type": "object"
}

Response

200

application/json

Successful Response

One of an app's entities and its stored JSON Schema.

entity_name · string · required

Name of the entity.

Example:

"Invoice"

entity_schema · Entity Schema · object · required

The entity's stored JSON Schema, including its properties, required fields, and any row-level security rules under rls. For the app's own entities it also carries a name key holding the entity name. For User it holds only the custom fields added on top of the built-in ones, and has no name key.

Example:

{
  "name": "Invoice",
  "properties": {
    "amount": {
      "description": "Total amount in cents",
      "type": "number"
    },
    "status": {
      "enum": ["draft", "sent", "paid"],
      "type": "string"
    }
  },
  "required": ["amount"],
  "rls": {
    "read": { "created_by": "{{user.email}}" }
  },
  "type": "object"
}