DTM docs
HomeDor Traffic MinerMetagraphDTM AppMarketingAPI
API
API
  • Overview
  • Authentication
    • Basic Auth
    • Manually Creating Basic Auth Headers
  • Response Format
    • Successful Responses
    • Error Responses
  • Pagination
  • Datetimes
    • Datetime Formats
    • Datetimes Grouped by Local Time Zone
  • Rate Limiting
  • Syncing Data
    • Asynchronous Data
    • Querying by Update Timestamp
  • Data Validity
    • Validity
    • Completeness
  • Endpoints
    • Organizations
      • GET /organizations
      • GET /organizations/{org_id}
    • Locations
      • GET /locations
      • GET /locations/{location_id}
      • GET /locations/{location_id}/devices
      • POST /locations
      • DELETE /locations/{location_id}
    • Devices
      • GET /devices
      • GET /devices/{serial_number}
      • PUT /devices/{serial_number}
      • POST /devices/{serial_number}/install
      • POST /devices/{serial_number}/uninstall
      • GET /uninstalled-devices
    • Foot Traffic
      • GET /foot-traffic/locations
      • GET /foot-traffic/devices/{serial_number}
    • Schemas
      • Organization
      • Location
      • Address
      • Device
      • LocationMetric
      • Foot Traffic
Powered by GitBook
On this page

Pagination

Endpoints that return a list of resources are paginated if results exceed the maximum length defined for the endpoint. Dor uses a cursor-based pagination strategy for all list endpoints.

The next key in the meta response object will either be NULL or contain a link. If it is NULL, there are no additional results available for your query. If it contains a link, follow the link for the next page of results for your query. Continue following the next link returned with each subsequent request to fetch all available results.

"data": [
    {...},
    {...}
],
"meta": {
    "limit": 100,
    "next": "https://api.getdor.com/v2/locations?next=2lkj23jf2fljf29"
}    

PreviousError ResponsesNextDatetimes

Last updated 1 year ago