# Offset / pagination for \`documents/search\` (and \`/query\`)

**URL:** <https://community.pinecone.io/t/offset-pagination-for-documents-search-and-query/8529>\
**Category:** Feature Requests\
**Tags:** vector-database\
**Created:** [November 5, 2026, 7:05am UTC](https://community.pinecone.io/t/offset-pagination-for-documents-search-and-query/8529 "2026-11-05T07:05:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![scotteuser](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/scotteuser/32/4219_2.png) [@scotteuser](https://community.pinecone.io/u/scotteuser)\
**Post date:** [November 5, 2026, 7:05am UTC](https://community.pinecone.io/t/offset-pagination-for-documents-search-and-query/8529/1 "2026-11-05T07:05:18Z")

</div>

The new Documents API endpoints do not support offset or a pagination token like the Vector API endpoints do.

So the only way we can do pagination e.g. for page 2 is fetch 2x the amount and slice at the moment.

It seems like a bit of a regression and will cause us issues with the Drupal Search API/AI Search integration (I’m the primary maintainer of AI Search there + the AI VDB Provider Pinecone modules).

---

<div class="post-metadata">

**Author:** ![scotteuser](https://sea2.discourse-cdn.com/flex020/user_avatar/community.pinecone.io/scotteuser/32/4219_2.png) [@scotteuser](https://community.pinecone.io/u/scotteuser)\
**Post date:** [November 5, 2026, 7:08am UTC](https://community.pinecone.io/t/offset-pagination-for-documents-search-and-query/8529/2 "2026-11-05T07:08:32Z")

</div>

Issue in Drupal Gitlab queue here [Client Challenge](https://git.drupalcode.org/project/ai_vdb_provider_pinecone/-/work_items/3586217)