> ## Documentation Index > Fetch the complete documentation index at: https://docs.hologram.io/llms.txt > Use this file to discover all available pages before exploring further. # List daily aggregated data usage ## OpenAPI ````yaml /api/1/openapi.yaml get /usage/data/daily openapi: 3.0.0 info: title: Hologram REST API v1 description: >- The Hologram HTTP API is a REST-style interface for managing Hologram devices, accounts, and cloud data. Using the Hologram REST API, you can activate SIMs, get your devices approximate location, send SMS to your devices, update a device's usage limit, and much more. ## Authentication Hologram supports **HTTP Basic authentication** using API keys. Simply set the username of the request to `apikey`. The password field is the API key itself. You can find your API key on the Hologram Dashboard under [Account Settings](https://dashboard.hologram.io/settings/api). Your API key gives you access to your personal account, as well as any organizations you are a member of. Make sure you don't store your API key in a publicly accessible place like GitHub. If you are a member of multiple organizations, many endpoints accept an `orgid` argument to filter for devices or other objects within a specific organization. You can find your `orgid` by following [this guide from our Help Center](https://support.hologram.io/hc/en-us/articles/360035421234-What-is-my-organization-ID-orgid). ### Header Example ``` curl --verbose GET \ 'https://dashboard.hologram.io/api/1/users/me' \ -u apikey:YOUR_API_KEY ``` You can also base64 encode "apikey:YOUR_API_KEY" and include it directly in the header. ``` curl --verbose GET \ 'https://dashboard.hologram.io/api/1/users/me' \ --header "Authorization: Basic BASE64(apikey:YOUR_API_KEY)" ``` ## Requests Request bodies can be provided in either JSON or form-urlencoded formats. Please note that the examples in this documentation will only display JSON bodies. ### **JSON body** ``` curl --verbose --request POST \ --header "Content-Type: application/json" \ --header "Authorization: Basic BASE64(apikey:YOUR_API_KEY)" \ --data '{"deviceid": 56668, "body": "Hello device!"}' \ 'https://dashboard.hologram.io/api/1/sms/incoming' ``` ### **form-urlencoded body** ``` curl --verbose --request POST \ --header "Content-Type: application/x-form-urlencoded" \ --header "Authorization: Basic BASE64(apikey:YOUR_API_KEY)" \ --data 'deviceid=56668&body=Hello%20device!' \ 'https://dashboard.hologram.io/api/1/sms/incoming' ``` ## Responses All API responses are returned as JSON objects with the following fields: * `success` (boolean) - Indicates whether the request was successful. * `data` (object or array) - Contains the requested data or information about the operation that was performed. Only present when `success` is true. * `error` (string) - Information about why the request failed. Only present when `success` is false. Most GET responses will also include the following fields if a limit is included as part of the query string: * `limit` (number) - The query limit, some have this value built in and others often have a maximum value that the limit can be * `size` (number) - The number of values returned by the query * `continues` (boolean, optional) - This is only returned if there are more values than were returned * `links` (array) - Contains information related to the query performed * `path` (string) - The API endpoint path * `base` (string) - API base URL * `next` (string) - URL with query string to get the next results Note that all dates and times are returned in UTC. ## Rate Limiting In order to provide a good quality of service to all of our customers, we enforce a rate limit on all API requests. If you exceed the rate limit you will receive a HTTP 429 response with a JSON response body like this: ``` { "success":false, "error":"API rate limit exceeded" } ``` If you receive this response, you should refrain from making requests for 5-10 seconds and then retry the request. Hologram's REST API provides methods to perform many requests in bulk. For example, you can change the data plans of multiple SIMs at once using https://dashboard.hologram.io/api/1/links/cellular/changeplan. If there is request you would like to make in bulk but cannot, please reach out to [support@hologram.io](mailto:support@hologram.io) for assistance. version: '1' servers: - url: https://dashboard.hologram.io/api/1 description: Hologram REST API v1 security: [] tags: - name: Devices description: Devices - name: SIM Configuration description: SIM Configuration x-group: SIM Configuration - Conductor - name: Organizations description: Organizations - name: Personal account description: Personal account - name: Async Change Requests description: Async Change Requests paths: /usage/data/daily: get: tags: - Devices summary: List daily aggregated data usage operationId: getDailyUsage parameters: - name: limit in: query description: Maximum number of results to return (max 5000) required: false schema: type: integer default: 100 maximum: 5000 - name: before in: query description: >- Return records with ID less than this value (cursor-based pagination) required: false schema: type: integer - name: after in: query description: >- Return records with ID greater than this value (cursor-based pagination) required: false schema: type: integer - name: linkid in: query description: Filter by a specific cellular link (SIM profile) ID required: false schema: type: integer - name: linkids in: query description: Comma-separated list of link (SIM profile) IDs to filter by required: false schema: type: string - name: tagids in: query description: Comma-separated list of device tag IDs to filter by required: false schema: type: string - name: timestart in: query description: Unix timestamp; return records from this time onward required: false schema: type: integer - name: timeend in: query description: Unix timestamp; return records up to this time required: false schema: type: integer - name: islive in: query description: When true, include only live (non-paused) devices required: false schema: type: boolean - name: aggregateall in: query description: >- When true, aggregate usage across all matching records into a single row required: false schema: type: boolean - name: startat in: query description: Return results with record ID less than this value required: false schema: type: string - name: tagid in: query description: Filter by device tag ID required: false schema: type: integer - name: tagname in: query description: Filter by device tag name required: false schema: type: string - name: dataplansubscriptionid in: query description: Filter by data plan subscription ID required: false schema: type: integer responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/UsageDailyListResponse' '401': description: Unauthorized security: - apiKeyAuth: [] components: schemas: UsageDailyListResponse: properties: success: $ref: '#/components/schemas/SuccessProperty' limit: description: Maximum number of records returned per page type: integer size: description: Number of records in this response type: integer continues: description: True if more records are available type: boolean lastid: description: >- record_id of the last record returned; pass as startat to fetch the next page type: integer links: $ref: '#/components/schemas/PaginationLinks' data: type: array items: $ref: '#/components/schemas/UsageDailyRecord' type: object SuccessProperty: description: Indicates whether the request was successful. type: boolean example: true PaginationLinks: properties: path: description: The API endpoint path type: string base: description: The API base URL type: string next: description: URL to retrieve the next page of results type: string type: object UsageDailyRecord: properties: linkid: description: Cellular link (SIM) ID type: integer record_id: description: Unique daily record ID, used for cursor-based pagination type: integer date: description: Usage date (YYYY-MM-DD) type: string bytes: description: Total bytes used on this date type: integer session_count: description: Number of data sessions on this date type: integer reporting_windows_with_usage: description: Number of reporting windows that recorded usage type: integer type: object securitySchemes: apiKeyAuth: type: http description: >- HTTP Basic authentication using API keys. Set the username to `apikey` and the password to your API key. You can find your API key on the Hologram Dashboard under Account Settings. scheme: basic ````