Pagination

	Example use

	GET /api/leads?page=2&limit=10&rest_api_key=your_md5_encoded_key

	GET /api/bridges?page=1&limit=20&rest_api_key=your_md5_encoded_key

	GET /api/areacodes?page=3&limit=50&rest_api_key=your_md5_encoded_key
	
	GET /api/areacodes?page=3&limit=50&rest_api_key=your_md5_encoded_key
	
	GET /api/users?page=2&limit=25&rest_api_key=your_md5_encoded_key
                

Pagination and limit are techniques used in APIs and web applications to manage and display large sets of data in a more organized and user-friendly way. Pagination involves dividing a large dataset into smaller "pages" of data, allowing users to view a specific subset of records at a time. This prevents overwhelming the user with all the data at once and makes navigation more efficient.

The "limit" refers to the maximum number of records displayed on each page. For instance, if there are 100 records and the limit is set to 10, each page will show 10 records. When you reach the end of a page, you can navigate to the next page to see the next set of records. This process continues until you've seen all the data.

In summary, pagination and limit work together to enhance user experience when dealing with a large amount of data, making it easier to explore and interact with information systematically.

Pagination Variables

The below variables are defined in the query string of the url. The max records per page is capped at 500. 30 to 60 is recommended.

Field	Type	Description
page	String	(optional) query result page number to retrieve
limit	String	(optional) Query result rows per page. Max 500 (recommended 30)