# Async endpoints return different status for List vs Get on /completions endpoint

**URL:** <https://community.perplexity.ai/t/async-endpoints-return-different-status-for-list-vs-get-on-completions-endpoint/3681>\
**Category:** Bug Reports\
**Created:** [January 26, 2026, 2:15am UTC](https://community.perplexity.ai/t/async-endpoints-return-different-status-for-list-vs-get-on-completions-endpoint/3681 "2026-01-26T02:15:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cfdude](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/cfdude/32/2507_2.png) [@cfdude](https://community.perplexity.ai/u/cfdude)\
**Post date:** [January 26, 2026, 2:15am UTC](https://community.perplexity.ai/t/async-endpoints-return-different-status-for-list-vs-get-on-completions-endpoint/3681/1 "2026-01-26T02:15:59Z")

</div>

I need to report a bug I found in the API for Async calls, here is the details: I tested Perplexity’s API directly using curl:

# Direct curl to Perplexity’s LIST endpoint  
curl “[https://api.perplexity.ai/async/chat/completions?limit=5](https://api.perplexity.ai/async/chat/completions?limit=5)”

# Returns: status: “COMPLETED”, completed\_at: 1769385424

# Direct curl to Perplexity’s GET endpoint  
curl “[https://api.perplexity.ai/async/chat/completions/](https://api.perplexity.ai/async/chat/completions/33d2f3b2-e5bd-413d-a1ef-ada898e37507)[id]”

# Returns: status: “IN\_PROGRESS”, completed\_at: null

Same API key, same job ID, same moment in time - two different answers from Perplexity’s servers.