OpenFGA SDK doesn't seem to support async_req parameter #194

Activity

1. dandua98-cohere

   added

   bugSomething isn't workingSomething isn't working

   on May 23, 2025
2. github-project-automation

   moved this to Backlog in SDKs and Toolingon May 23, 2025
3. github-project-automation

   added this to SDKs and Toolingon May 23, 2025
4. dyeam0

   moved this from Backlog to Intake in SDKs and Toolingon Aug 27, 2025
5. Abishek-Newar commented on Jan 23, 2026

   

   Abishek-Newar

   on Jan 23, 2026

   Contributor

   More actions

   Hi @dandua98-cohere , I'd like to work on this issue. Would a PR to expose async_req through
   options_to_kwargs be welcome?

   😕React with 😕1Reacted by Anurag Bandyopadhyay
6. emilic commented on Mar 24, 2026

   

   emilic

   on Mar 24, 2026

   More actions

   Thanks for the contribution! However, I don't think we should add async_req support to the SDK.

   The async_req parameter is a legacy pattern from OpenAPI Generator that uses threading (ThreadPool) under the hood. The Python SDK already provides a dedicated async client built on asyncio/aiohttp, which is the modern and recommended way to handle async operations in Python.

   For example, you can use the async client today:

   async with OpenFgaClient(configuration) as fga_client:
       # Single async call
       response = await fga_client.check(request)
   
       # Concurrent calls
       results = await asyncio.gather(
           fga_client.check(request_1),
           fga_client.check(request_2),
           fga_client.check(request_3),
       )
   

   This gives you everything async_req would, with better performance characteristics and no threading overhead.

   If there's a specific use case that the async client doesn't cover, we'd love to hear about it — happy to discuss further.