# Getting response code 400 - bad request requesting Deals on API v3 **URL:** \ **Category:** APIs & Integrations\ **Tags:** object\ **Created:** [February 5, 2020, 2:44pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580 "2020-02-05T14:44:24Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![SAMsan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samsan/32/17908_2.png) [@SAMsan](https://community.hubspot.com/u/SAMsan)\ **Post date:** [February 5, 2020, 2:44pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/1 "2020-02-05T14:44:24Z")
Hello, I’m trying to request deals per Pipeline using API v3 Search method. I can get entries at some point. Using “after”=999 is working but “after”=9999 fails returning 400 - bad request. Here are the logs : ```auto {limit=100.0, filters=[{propertyName=pipeline, value=571502.0, operator=EQ}], after=999, sorts=[{propertyName=createdate, direction=ASCENDING}], properties=[dealname, amount, dealstage, sign_par, hubspot_owner_id, rdv_vecu, produit_vendu, type_de_produit, statut_dossier, origine, motif_de_contact, raison_des_clotures, lead_brut_lead_net_contacts, url_site]} ----- RETURN ----- UrlFetchApp result: 200.0 {total=10875, paging={next={after=1099}}} {limit=100.0, filters=[{propertyName=pipeline, value=571502.0, operator=EQ}], after=9999, sorts=[{propertyName=createdate, direction=ASCENDING}], properties=[dealname, amount, dealstage, sign_par, hubspot_owner_id, rdv_vecu, produit_vendu, type_de_produit, statut_dossier, origine, motif_de_contact, raison_des_clotures, lead_brut_lead_net_contacts, url_site]} ----- RETURN ----- UrlFetchApp Failed: 400.0 {"status":"error","message":"There was a problem with the request.","correlationId":"27d1f756-d1ee-4943-a4e4-610611b1a0b6","requestId":"412b9bca-7814-41f4-9fb4-72d1ebb76215"} ``` Obviously, I won’t be able to request all my deals… ---
**Author:** ![Willson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/willson/32/84663_2.png) [@Willson](https://community.hubspot.com/u/Willson)\ **Post date:** [February 5, 2020, 3:16pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/2 "2020-02-05T15:16:23Z")
Hi @SAMsan In order to assist, would you be able to forward on the exact Request URL you’re currently using and the associated v3 documentation you’re referencing too for me? Thanks! ---
**Author:** ![SAMsan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samsan/32/17908_2.png) [@SAMsan](https://community.hubspot.com/u/SAMsan)\ **Post date:** [February 5, 2020, 3:27pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/3 "2020-02-05T15:27:22Z")
Thank you @Willson The request url I use is : [https://api.hubapi.com/crm/v3/objects/deals/search?hapikey=\*\*myAPIkey\*\*](https://api.hubapi.com/crm/v3/objects/deals/search?hapikey= **myAPIkey** ) I am using this documentation page : > **[Accounts Dashboard | HubSpot](https://app.hubspot.com/myaccounts?next=developerdocs&redirect=%2Fdocs-beta%2Fcrm%2Fsearch)** ---
**Author:** ![DZaboronsky](https://avatars.discourse-cdn.com/v4/letter/d/8c91f0/32.png) [@DZaboronsky](https://community.hubspot.com/u/DZaboronsky)\ **Post date:** [April 23, 2024, 9:17am UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/4 "2024-04-23T09:17:21Z")
Hello, are there any updates? This issue is 2 years old and still exists on the search enpoint as far as I can see? (experiencing on the contacts search endpoint). Also this limit is not documented here: [API usage guidelines and limits - HubSpot docs](https://developers.hubspot.com/docs/api/usage-details#rate-limits) under `other limits`. Just wondering what is the correct method to handle big resposnes? I can see it is in the docs at: [Search the CRM - HubSpot docs](https://developers.hubspot.com/docs/api/crm/search) but there is no suggestion for work around, and as it looks on this thread this is a known limitiation which is now ~4 years old? ---
**Author:** ![Willson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/willson/32/84663_2.png) [@Willson](https://community.hubspot.com/u/Willson)\ **Post date:** [February 5, 2020, 3:34pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/5 "2020-02-05T15:34:52Z")
Hi @SAMsan Thanks for providing this! To confirm, the `after` parameter is used to access the next page of results and the value entered is the `paging.next.after` property seen in the previous response. If the `paging.next.after` property isn’t provided, there are no additional results to display. As you’re searching Deals in your Pipelines, I would not expect you to be fetching this many results that the `paging.next.after` value returned is 9999. Can you confirm? ---
**Author:** ![SAMsan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/samsan/32/17908_2.png) [@SAMsan](https://community.hubspot.com/u/SAMsan)\ **Post date:** [February 5, 2020, 4:16pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/6 "2020-02-05T16:16:49Z")
@Willson I do indeed receive the after parameter once the first limit is reached. My code loops until the after parameter is absent. As I request all deals from one pipeline for analytics purpose, request’s total items is above 10k. Thank you for your help ---
**Author:** ![Willson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/willson/32/84663_2.png) [@Willson](https://community.hubspot.com/u/Willson)\ **Post date:** [February 6, 2020, 10:20am UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/7 "2020-02-06T10:20:06Z")
Hi @SAMsan I just wanted to follow-up here! I am looking into this further from my end and will revert with an update once I have more for you. Feel free to add any questions you may have in the meantime. Thanks ---
**Author:** ![Willson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/willson/32/84663_2.png) [@Willson](https://community.hubspot.com/u/Willson)\ **Post date:** [February 6, 2020, 4:31pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/8 "2020-02-06T16:31:04Z")
Hey @SAMsan Thanks for your patience here! I was able to dig into this internally and find that this is a known limitation currently, as such, we’ve updated the new documenation to include this now. The new limitation reads: `The search endpoints are limited to 10,000 total results in the response. Attempting to page beyond 10,000 will generate a 400 error.` See here: [Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs-beta/crm/search) I hope this helps! ---
**Author:** ![saps](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/saps/32/49304_2.png) [@saps](https://community.hubspot.com/u/saps)\ **Post date:** [July 23, 2021, 8:14am UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/9 "2021-07-23T08:14:50Z")
Hi @Willson , when will this issue be resolved? While it isn’t a big problem for Deals, it is a massive problem for Contacts - the Contacts API (without filterable results) provides too much information from past (years/months) whereas the Search API gives too less. Having more than 10k active Contacts is pretty normal and not an edge case. ---
**Author:** ![StanBartczak](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stanbartczak/32/10239_2.png) [@StanBartczak](https://community.hubspot.com/u/StanBartczak)\ **Post date:** [September 13, 2022, 11:30am UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/10 "2022-09-13T11:30:06Z")
Hi @Willson is there no way to only check the number of contacts/deals matching some criteria if there are more than 10k results? ---
**Author:** ![adley\_amzovski](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/adley_amzovski/32/84335_2.png) [@adley\_amzovski](https://community.hubspot.com/u/adley_amzovski)\ **Post date:** [November 30, 2020, 7:43pm UTC](https://community.hubspot.com/t/getting-response-code-400-bad-request-requesting-deals-on-api-v3/18580/11 "2020-11-30T19:43:11Z")
Hi @Willson Is there a timeline to fix this limitation? We have updates of 800K contacts to be pulled on a daily basis that we’re filtering using the lastmodifieddate param. Do you have a better solution to achieve the data pulls?