#Pagination

The pagination.conf file defines default and maximum pagination limits used by Enterprise list endpoints that support limit, offset, and, on some endpoints, sort.

#Configuration

{
  "defaultLimit": 100,
  "maxLimit": 1000
}

#Fields

• defaultLimit: applied when limit is not provided by the client.
• maxLimit: upper bound accepted for limit.

offset is not configurable — it always defaults to 0 when omitted.

#Query parameters

• limit (integer, optional): number of entries to return. Defaults to defaultLimit; must be greater than 0 and less than or equal to maxLimit.
• offset (integer, optional): number of entries to skip. Defaults to 0; must be greater than or equal to 0.
• sort (string, optional): only accepted on endpoints marked Sortable in the table below. Supported values:
  • createdDateTime or createdDateTime- — newest created first (the bare value is shorthand for -, descending)
  • createdDateTime+ — oldest created first (ascending)
  • updatedDateTime or updatedDateTime- — most recently updated first (descending)
  • updatedDateTime+ — least recently updated first (ascending)
  
  Passing sort on an endpoint that isn't marked Sortable returns 400 Bad Request. When sort is omitted, each endpoint falls back to its own default order, which isn't necessarily insertion order — pass sort explicitly if your client depends on ordering.

#Validation behavior

For list endpoints using this pagination contract, the API returns 400 Bad Request when:

• limit <= 0
• limit > maxLimit
• offset < 0
• limit or offset is not an integer
• sort is provided on an endpoint that doesn't support it
• sort is provided with a value outside the supported list above

#Endpoint behavior

The following list endpoints support this contract:

Responses remain arrays (no pagination envelope is added).

See also: List Service Resources and Manage Certificates for worked examples.