POST /vectors/update
Update a vector in a namespace. If a value is included, it will overwrite the previous value. If a set_metadata is included, the values of the fields specified in it will be added or overwrite the previous value.
For guidance and examples, see Update data.
Servers
- https://{index_host}
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
X-Pinecone-Api-Version |
String | Yes |
Required date-based version header Default value: "2025-10" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | No |
Vector's unique id. |
values[] |
Array | No |
Vector data. |
namespace |
String | No |
The namespace containing the vector to update. |
filter |
Object | No |
A metadata filter expression. When updating metadata across records in a namespace, the update is applied to all records that match the filter. See Understanding metadata. |
setMetadata |
Object | No |
Metadata to set for the vector. |
dryRun |
Boolean | No |
If Default value: false |
sparseValues |
Object | No |
Vector sparse data. Represented as a list of indices and a list of corresponded values, which must be with the same length. |
sparseValues.values[] |
Array | Yes |
The corresponding values of the sparse data, which must be with the same length as the indices. |
sparseValues.indices[] |
Array | Yes |
The indices of the sparse data. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.