# Text2vec-openai Batch API

**URL:** <https://forum.weaviate.io/t/text2vec-openai-batch-api/2953>\
**Category:** Support\
**Tags:** integration, wcs, python\
**Created:** [July 6, 2024, 12:40am UTC](https://forum.weaviate.io/t/text2vec-openai-batch-api/2953 "2024-07-06T00:40:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SmitNGRA](https://avatars.discourse-cdn.com/v4/letter/s/e47c2d/32.png) [@SmitNGRA](https://forum.weaviate.io/u/SmitNGRA)\
**Post date:** [July 6, 2024, 12:40am UTC](https://forum.weaviate.io/t/text2vec-openai-batch-api/2953/1 "2024-07-06T00:40:35Z")

</div>

### Description

I have been using Weaviate free 14 day cluster and am trying to use OpenAI embeddings and store in a Weaviate collection. OpenAI’s website mentions about having a Batch API where there are higher rate-limits and the resulting embeddings are ready after 24 hours (at a 50% cost of the original real-time vector generation which is right now 3 requests per minute)

Is there a way to configure the Weaviate vectorizer using the same OpenAI batch API?  
More details are here  
[Batch - OpenAI API](https://platform.openai.com/docs/guides/batch)

### Server Setup Information

- Client Language and Version: Python
- Multitenancy: No

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [July 8, 2024, 11:55am UTC](https://forum.weaviate.io/t/text2vec-openai-batch-api/2953/2 "2024-07-08T11:55:38Z")

</div>

hi @SmitNGRA ! Welcome to our community 🤗

AFAIK, we do not have this implemented. Yet.

I have found this Github issue that is related:

> <https://github.com/weaviate/weaviate/issues/4587>
>
> \### Describe your feature request
> 
> With async indexing being released, the bottl…eneck to import data has moved to the vectorizer modules which often require 3rd party api calls to convert text/image chunks into vectors. There has been recent work https://github.com/weaviate/weaviate/pull/4546 https://github.com/weaviate/weaviate/pull/4578 to switch vectorizer modules to use batching wherever possible. We can further reduce import times by enabling async indexing at the module level as well.
> 
> At a high level:
> 
> \- \[\] Switch to async indexing straight to disk https://github.com/weaviate/weaviate/pull/3974.
> \- \[\] If a module is enabled, async workers should read a batch of objects from disk (not vectors), use the module's \`BatchVectorizer\` to generate the vectors, and then write to the vector index as usual.
> \- \[\] There needs to be a solution for persistent failures including surfacing errors to users.
> 
> 
> 
> 
> \### Code of Conduct
> 
> \- \[X\] I have read and agree to the Weaviate's \[Contributor Guide\](https://weaviate.io/developers/contributor-guide) and \[Code of Conduct\](https://weaviate.io/service/code-of-conduct)

Please, leave your thumbs up 👍 there so we can track it’s popularity!

Thanks!