Inbound REST API GET call fails when sysparm_limit=0Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Error message 'sysparm_limit value must be a positive integer' is seen when making inbound REST API GET call with sysparm_limit=0 Release London Cause sysparm_limit is used to specify maximum number of records to be returned in the response. Setting it to 0 is considered invalid and this causes the request to fail. Resolution If you are trying to retrieve less than 10,000 rows you can just remove the sysparm_limit from the query. The system by default has a limit of 10,000. If the result is more than 10,000 the "x-total count" header in response contains the total number of records for the query. You can use this and make as many calls needed to get all the records. Note: The limit parameter defaults to 10,000 records. This limit can be set to any value. Be aware, however, that an unusually large value can impact system performance. X-Total-Count Total count of records returned by the query. The best practice to retrieve large number of records is by using pagination. You may follow the steps provided in KB0727636.