--- id: insert title: 'Create data: insert()' slug: insert custom_edit_url: https://github.com/supabase/supabase/edit/master/spec/supabase_js_v1_legacy.yml --- import Tabs from '@theme/Tabs' import TabItem from '@theme/TabItem' Performs an INSERT into the table. ```js const { data, error } = await supabase .from('cities') .insert([{ name: 'The Shire', country_id: 554 }]) ``` ## Parameters ## Notes - By default, every time you run `insert()`, the client library will make a `select` to return the full record. This is convenient, but it can also cause problems if your Policies are not configured to allow the `select` operation. If you are using Row Level Security and you are encountering problems, try setting the `returning` param to `minimal`. ## Examples ### Create a record ```js const { data, error } = await supabase .from('cities') .insert([{ name: 'The Shire', country_id: 554 }]) ``` ### Bulk create When running a bulk create, the operation is handled in a single transaction. If any of the inserts fail, all other operations are rolled back. ```js const { data, error } = await supabase.from('cities').insert([ { name: 'The Shire', country_id: 554 }, { name: 'Rohan', country_id: 555 }, ]) ``` ### Upsert For upsert, if set to true, primary key columns would need to be included in the data parameter in order for an update to properly happen. Also, primary keys used must be natural, not surrogate. There are however, [workarounds](https://github.com/PostgREST/postgrest/issues/1118) for surrogate primary keys. ```js const { data, error } = await supabase.from('cities').insert( [ { name: 'The Shire', country_id: 554 }, { name: 'Rohan', country_id: 555 }, { name: 'City by the Bay', country_id: 840 }, ], { upsert: true } ) ```