The most recent messages in the time range are returned first. The messages array contains up to 100 messages between the oldest and latest timestamps. This form of pagination can be used in conjunction with cursors. By using this value as a cursor parameter in a subsequent request, along with limit, you may navigate through the collection page by virtual page. Responses will include a top-level response_metadata attribute containing a next_cursor value. We recommend no more than 200 results at a time.
To begin pagination, specify a limit value under 1000. This method uses cursor-based pagination to make it easier to incrementally collect information. The calling app must also have the relevant *:history scope for the conversation type. Every other type of token can be used with this method for any conversations the relevant app, bot, or user is a member of.Apps using classic bot user token may use this method for direct message and multi-party direct message conversations but lack sufficient permissions to use this method on public and private channels.The scopes and token types required to use this method vary by conversation type: To read the entire history for a conversation, call the method with no oldest or latest arguments, and then continue paging using the instructions below. This method returns a portion of message events from the specified conversation.