# REST v2 - List Endpoints - Ability to provide an Array of ID Numbers

**URL:** <https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997>\
**Category:** API Q&A\
**Created:** [March 17, 2026, 6:13pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997 "2026-03-17T18:13:01Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [March 17, 2026, 6:13pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/1 "2026-03-17T18:13:01Z")

</div>

@OmarAlmonte - Another issue to be added to the tracker.

In the XML-RPC you can provide an array of ID numbers to the tables so that you can return the results specific to other ID numbers. This is very useful when cross referencing the data between the tables.

in REST v2, I do not see the ability to do any of that. None of the main endpoints, eg: Contacts, Opportunities, Orders, Notes, Products, Tags, etc, can do it.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [March 17, 2026, 8:15pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/2 "2026-03-17T20:15:40Z")

</div>

Thanks for the feedback! I’ll raise this internally and will also add it to the tracker.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [April 27, 2026, 7:59pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/3 "2026-04-27T19:59:46Z")

</div>

Hi @Pav,

Just a quick update on REST v2 filtering:

The Orders list endpoint now supports filtering by multiple order IDs using the `ids` filter, allowing you to retrieve specific orders in bulk.

The Products list endpoint now supports filtering by multiple product IDs, enabling retrieval of multiple products in a single request.

Docs for reference:

> **[Keap REST API](https://developer.infusionsoft.com/docs/restv2/#tag/Orders/operation/listOrders)**

> **[Keap REST API](https://developer.infusionsoft.com/docs/restv2/#tag/Products/operation/listProducts)**

Thanks again for highlighting these use cases.

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [April 27, 2026, 8:14pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/4 "2026-04-27T20:14:17Z")

</div>

What about the other endpoints like Payments?

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [April 27, 2026, 8:22pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/5 "2026-04-27T20:22:52Z")

</div>

We’re currently working on enhancing the filtering capabilities across most of the list endpoints. I’ll keep you updated as soon as support for these additional items is released.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [May 11, 2026, 2:38pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/6 "2026-05-11T14:38:24Z")

</div>

Hi @Pav,

Quick update, filtering by multiple IDs is now also supported for Opportunities and Contacts via the `ids` filter on the list endpoints.

Documentation: [Keap REST API](https://developer.infusionsoft.com/docs/restv2/)

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [May 11, 2026, 2:58pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/7 "2026-05-11T14:58:39Z")

</div>

@OmarAlmonte, thanks, but a couple of things have been spotted.

**Contacts**

- There is now 2 fields called “ids” and “contact\_ids”. Is the last one a mistake?
- What is the limit of the IDs?

**Opportunities**

- Why is there a limit of 100 IDs, whereas 1000 can be provided in XML-RPC?

Are there any other List Endpoints that have varying ID limits?

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [May 11, 2026, 5:47pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/8 "2026-05-11T17:47:23Z")

</div>

Hi Pav, great questions.

For Contacts, both `ids` and `contact_ids` are supported. `ids` is the preferred V2 standard. They work the same, but don’t mix them in the same request or you’ll get a 400 error.

For Opportunities, the `ids` filter is currently capped at 100 for performance reasons.

I’ll flag the Opportunities limit for a consistency review.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [June 1, 2026, 1:24pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/9 "2026-06-01T13:24:15Z")

</div>

Hi @Pav,

Quick update, filtering by multiple IDs is now also supported for Payments, Tasks and Notes via the ids filter on the list endpoints.

Docs: [Keap REST API](https://developer.infusionsoft.com/docs/restv2/)

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [June 1, 2026, 2:07pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/10 "2026-06-01T14:07:47Z")

</div>

@OmarAlmonte, what is the limit? 100 or 1,000?

Also, when you are planning to support multiple Order IDs?

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [June 1, 2026, 2:26pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/11 "2026-06-01T14:26:48Z")

</div>

The limit is 1,000. Filtering by multiple Order IDs is already supported in the List Orders endpoint.

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [June 1, 2026, 2:35pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/12 "2026-06-01T14:35:26Z")

</div>

I meant filtering of Order IDs on the Payments Endpoint.

I have an integration that pulls financial records from Keap. The Invoice IDs are picked up and supplied to either the InvoicePayment or Payment tables in XML-RPC. There is no equivalent in REST.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [June 1, 2026, 2:40pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/13 "2026-06-01T14:40:36Z")

</div>

You can use the V2 List Order Payments or List Payments endpoint and filter by a single Order ID. It will require more calls, but you can still achieve the same result.

---

<div class="post-metadata">

**Author:** ![Pav](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/pav/32/124_2.png) [@Pav](https://integration.keap.com/u/Pav)\
**Post date:** [June 1, 2026, 2:55pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/14 "2026-06-01T14:55:01Z")

</div>

Not practical when having to do several hundred every hour. It needs to support multiple IDs.

Or better still, why not add the Payments history to the Orders data, saves having to go to another endpoint to retrieve it.

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [June 18, 2026, 10:39pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/15 "2026-06-18T22:39:56Z")

</div>

Hi @Pav, the list payments endpoint now support filtering by multiple order IDs, thanks for your patience.  
Docs: [Keap REST API](https://developer.infusionsoft.com/docs/restv2/#tag/Sales/operation/listPayments)

---

<div class="post-metadata">

**Author:** ![OmarAlmonte](https://sea1.discourse-cdn.com/flex019/user_avatar/integration.keap.com/omaralmonte/32/15105_2.png) [@OmarAlmonte](https://integration.keap.com/u/OmarAlmonte)\
**Post date:** [July 2, 2026, 2:17pm UTC](https://integration.keap.com/t/rest-v2-list-endpoints-ability-to-provide-an-array-of-id-numbers/93997/16 "2026-07-02T14:17:15Z")

</div>

@Pav This is now supported by the list tags endpoint.
