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
  1. Response Format

Successful Responses

PreviousResponse FormatNextError Responses

Last updated 1 year ago

All API endpoints respond in a standard JSON response format for 2xx range HTTP responses. The root response object is split into two keys, data and meta.

The data key will contain an array of objects for plural endpoints or a single object for singular endpoints.

The meta key will contain information related to your request including any information required for the response.

{
  "data": [
    {...},
    {...}
  ],
  "meta": {
    ...
  }
}

paginating