POST /v1/embed

This endpoint returns text and image embeddings. An embedding is a list of floating point numbers that captures semantic information about the content that it represents.

Embeddings can be used to create classifiers as well as empower semantic search. To learn more about embeddings, see the embedding page.

If you want to learn more how to use the embedding model, have a look at the Semantic Search Guide.

Servers

https://api.cohere.com

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"
`X-Client-Name`	String	No	The name of the project that is making the request.

Request body fields

Name	Type	Required	Description
`input_type`	String	No	Specifies the type of input passed to the model. Required for embedding models v3 and higher. `"search_document"`: Used for embeddings stored in a vector database for search use-cases. `"search_query"`: Used for embeddings of search queries run against a vector DB to find relevant documents. `"classification"`: Used for embeddings passed through a text classifier. `"clustering"`: Used for the embeddings run through a clustering algorithm. `"image"`: Used for embeddings with image input. Valid values: `"search_document"` `"classification"` `"search_query"` `"image"` `"clustering"`
`embedding_types[]`	Array	No	Specifies the types of embeddings you want to get back. Not required and default is None, which returns the Embed Floats response type. Can be one or more of the following types. `"float"`: Use this when you want to get back the default float embeddings. Supported with all Embed models. `"int8"`: Use this when you want to get back signed int8 embeddings. Supported with Embed v3.0 and newer Embed models. `"uint8"`: Use this when you want to get back unsigned int8 embeddings. Supported with Embed v3.0 and newer Embed models. `"binary"`: Use this when you want to get back signed binary embeddings. Supported with Embed v3.0 and newer Embed models. `"ubinary"`: Use this when you want to get back unsigned binary embeddings. Supported with Embed v3.0 and newer Embed models.
`images[]`	Array	No	An array of image data URIs for the model to embed. The image must be a valid data URI. The image must be in either `image/jpeg`, `image/png`, `image/webp`, or `image/gif` format. Image embeddings are supported with Embed v3.0 and newer models. For Embed v3.x models, the maximum number of images per call is `1`, and each image has a maximum size of `5MB`. For Embed v4.0 and newer models, there is no limit on the number of images per call. The combined size of all images in the request must be at most `20MB`.
`texts[]`	Array	No	An array of strings for the model to embed. Maximum number of texts per call is `96`.
`truncate`	String	No	One of `NONE\|START\|END` to specify how the API will handle inputs longer than the maximum token length. Passing `START` will discard the start of the input. `END` will discard the end of the input. In both cases, input is discarded until the remaining input is exactly the maximum input token length for the model. If `NONE` is selected, when the input exceeds the maximum input token length an error will be returned. Valid values: `"START"` `"END"` `"NONE"` Default value: "END"
`model`	String	No	ID of one of the available Embedding models.

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.