Sign in

Create entity records

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

Adds several records to one of the app's entities in one call, and returns them in the order you sent them.

Send a JSON array of records, each written the same way as the body of Create entity record. Only the fields the entity's schema declares are stored, so a misspelled name is left out of the record instead of failing the call. Base44 always assigns id, created_date, updated_date, created_by, and created_by_id automatically, and ignores any of them you send. An empty array creates nothing and returns an empty array.

Every record is checked before any is written. If one record doesn't match the entity's schema, or the entity's rls create rule or a field-level rule doesn't cover it, the call is rejected and no records are created.

There's no fixed limit on how many records one call creates, but the whole array is written before the response comes back, so split a very large import into several calls.

Each record is new, so retrying a call that already succeeded creates every record again. If a call fails while it's writing, some of the records can already be stored, so check with List entity records before you retry.

Unlike Create entity record, this doesn't trigger the app's webhooks, automations, or workflows.

<Note>This endpoint accepts a personal API key belonging to a user with access to the app. A read-only key is refused, and workspace API keys are not accepted.</Note>

post/api/apps/{app_id}/entities/{entity_name}/bulk

Path parameters

app_idstring required

ID of the app that owns the entity.

ID of the app that owns the entity.

entity_namestring required

Name of the entity, exactly as List entity schemas reports it. Don't pass User here. It doesn't fail, but it reads and writes a separate, disconnected set of records stored under that name, not the app's real user accounts, which are managed through their own endpoints.

Name of the entity, exactly as List entity schemas reports it. Don't pass User here. It doesn't fail, but it reads and writes a separate, disconnected set of records stored under that name, not the app's real user accounts, which are managed through their own endpoints.

Request body

object[] required

The records to create, each a flat JSON object of the fields the entity's schema declares.

Response

The created records.

idstring nullable

ID of the record. Pass it as entity_id to Get entity record, Update entity record or Delete entity record.

created_datestring nullable

When the record was created, as a UTC timestamp in ISO 8601 format. A record Base44 has just created carries a Z suffix, and a record read back from storage does not.

updated_datestring nullable

When the record last changed, as a UTC timestamp in ISO 8601 format. A record Base44 has just created carries a Z suffix, and a record read back from storage does not.

created_bystring nullable

Email of the app user who created the record, or anonymous when a visitor created it on an app that needs no login. Apps that hide record authorship leave this field out of the response.

created_by_idstring nullable

ID of the app user who created the record, or anonymous when a visitor created it on an app that needs no login.

is_sampleboolean nullable

Whether Base44 stored the record as sample data while the app was being built. A record you create reports false.

Example response

[
  {
    "id": "6886b8d390dc7e2f4a2c91b3",
    "created_date": "2026-06-01T09:23:41.481000",
    "updated_date": "2026-06-04T14:07:02.115000",
    "created_by": "jane@acme.com",
    "created_by_id": "6874b0c2e1a94d0031bb77de"
  }
]

Changes

Changed in 1 of the 33 revisions of this API.1