Documentation menu
Docs / Guides / Filtering, search and pagination

Filtering, search and pagination

Narrow results with filters and full-text search, and page through large result sets.

Most ProcureData search endpoints accept query parameters to filter results, plus limit and offset to page through them.

Filter and search

Use q for full-text search across fields, and the endpoint-specific filters listed on each reference page. Combine as many as you need:

GET https://procuredata-canadian-government-procurement-api.p.rapidapi.com/sources?q=example&limit=50

Page through results

Responses include a count and an offset. Increase offset by your limit to walk the results:

GET https://procuredata-canadian-government-procurement-api.p.rapidapi.com/sources?limit=100&offset=0
GET https://procuredata-canadian-government-procurement-api.p.rapidapi.com/sources?limit=100&offset=100

Limits

limit is capped at 500 records per request, and offset at 9500. Asking for more returns a 422 or 400 explaining the ceiling.

Going past 9500 records

Offset paging stops at 9500. To walk a larger result set, pass the next_cursor from each response back as cursor on the next request, and keep going until next_cursor comes back null:

GET https://procuredata-canadian-government-procurement-api.p.rapidapi.com/sources?limit=500
GET https://procuredata-canadian-government-procurement-api.p.rapidapi.com/sources?limit=500&cursor=THE_NEXT_CURSOR_FROM_THE_LAST_RESPONSE

Cursor paging cannot be combined with sort_by=value, sort_by=published or sort_by=closing.

Ready to build?Subscribe on RapidAPI to get your key and start calling ProcureData in minutes.
Get your API key →