Insert / Update Records
Insert / Update Records
Insert and/or update the provided record(s) in the database.
<br>
### Optimizing Performance
**Batch Size**
When making PUT requests to operate on your data, determining an optimal batch size (number of records per request) can help increase overall throughput.
Depending on individual record size, an ideal batch size is typically between 50 - 150 records per request to balance throughput and API response time.
The following table displays performance based on an average individual record size of 1KB:
| Requests Per Minute | Batch Size (Rows Per Request) | Row Updates Per Minute |
| ------------------- | ----------------------------- | ---------------------- |
| Up to 1000 | 1 | 1000 |
| Up to 300 | 25 | 7500 |
| Up to 300 | 50 | 15000 |
| Up to 180 | 100 | 18000 |
| Up to 40 | 500 | 20000 |
<br>
Authentication
x-api-keystring
API Key authentication via header
Path parameters
db_id
Unique ID of the database
Request
\*\*The max payload size per request is 10MB, with a max individual record size of 5KB\*\* By default, all requests are queued for asynchronous processing. If synchronous processing is needed, the rate limit for requests is lower than for asynchronous processing. If export triggers have been set up, synchronous processing at the maximum rate, or with too many updates in a single request, may result in unexpected delays in export timing. If the system cannot process all outstanding requests synchronously, some requests may still be processed asynchronously even when synchronous processing is enabled.
Response
OK
status
API response status.
data
Errors
400
Bad Request Error
403
Forbidden Error
5XX
Server Error
502
Bad Gateway Error
