# GET /v1/async/sonar/{api\_request} returns the list of all requests instead of single request data

**URL:** <https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506>\
**Category:** Bug Reports\
**Tags:** sonar-api\
**Created:** [March 31, 2026, 2:25pm UTC](https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506 "2026-03-31T14:25:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikst](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/nikst/32/2898_2.png) [@nikst](https://community.perplexity.ai/u/nikst)\
**Post date:** [March 31, 2026, 2:25pm UTC](https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506/1 "2026-03-31T14:25:02Z")

</div>

## 🐛 Describe the Bug

API calls to GET /v1/async/sonar/{api\_request} return the same response as calls to GET /v1/async/sonar

## ✅ Expected Behavior

I expect the endpoint GET /v1/async/sonar/{api\_request} to return the data for the specific async request with the given ID.

## ❌ Actual Behavior

The endpoint GET /v1/async/sonar/{api\_request} returns a list of all my async requests.

## 🔄 Steps to Reproduce

1. Call the API using the following request: GET /v1/async/sonar/{api\_request}
2. Observe the unexpected behavior.

## 📌 API Request & Response

```bash
curl --location 'https://api.perplexity.ai/v1/async/sonar/9bb07b01-cbf3-4fec-9531-890ab8509a27' --header 'Authorization: Bearer'

```

```json
{
    "next_token": null,
    "requests": [
        {
            "id": "9bb07b01-cbf3-4fec-9531-890ab8509a27",
            "created_at": 1774957725,
            "started_at": null,
            "completed_at": 1774957832,
            "failed_at": null,
            "model": "sonar-deep-research",
            "status": "COMPLETED"
        }
    ]
}

```

The same response is returned for an invalid ID:

```bash
curl --location 'https://api.perplexity.ai/v1/async/sonar/abcdefg' --header 'Authorization: Bearer'

```

## 🌍 Environment

- **API Version:** sonar-deep-research
- **Operating System:** MacOS

---

<div class="post-metadata">

**Author:** ![blinard](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/blinard/32/2907_2.png) [@blinard](https://community.perplexity.ai/u/blinard)\
**Post date:** [April 2, 2026, 7:59am UTC](https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506/2 "2026-04-02T07:59:30Z")

</div>

Same here! Unable to retrieve the result of an async deepresearch.

---

<div class="post-metadata">

**Author:** ![blinard](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/blinard/32/2907_2.png) [@blinard](https://community.perplexity.ai/u/blinard)\
**Post date:** [April 7, 2026, 7:42am UTC](https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506/3 "2026-04-07T07:42:00Z")

</div>

Hey @nikst have you found a solution on your end?

---

<div class="post-metadata">

**Author:** ![Alex\_Romanov](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/alex_romanov/32/330_2.png) [@Alex\_Romanov](https://community.perplexity.ai/u/Alex_Romanov)\
**Post date:** [April 16, 2026, 10:32am UTC](https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506/4 "2026-04-16T10:32:38Z")

</div>

Hey @nikst, @blinard ! Are you still facing this issue?

---

<div class="post-metadata">

**Author:** ![nikst](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/nikst/32/2898_2.png) [@nikst](https://community.perplexity.ai/u/nikst)\
**Post date:** [April 24, 2026, 4:26pm UTC](https://community.perplexity.ai/t/get-v1-async-sonar-api-request-returns-the-list-of-all-requests-instead-of-single-request-data/4506/5 "2026-04-24T16:26:31Z")

</div>

I see that the issue is fixed, the endpoint returns the correct response