POST /vectors/upsert
Upsert vectors into a namespace. If a new value is upserted for an existing vector ID, it will overwrite the previous value.
For guidance, examples, and limits, see Upsert 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 |
|---|---|---|---|
namespace |
String | No |
The namespace where you upsert vectors. |
vectors[] |
Array | Yes |
An array containing the vectors to upsert. Recommended batch limit is up to 1000 vectors. |
vectors[].id |
String | Yes |
This is the vector's unique id. |
vectors[].values[] |
Array | No |
This is the vector data included in the request. |
vectors[].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. |
vectors[].sparseValues.values[] |
Array | Yes |
The corresponding values of the sparse data, which must be with the same length as the indices. |
vectors[].sparseValues.indices[] |
Array | Yes |
The indices of the sparse data. |
vectors[].metadata |
Object | No |
This is the metadata included in the request. |
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.