> ## Documentation Index > Fetch the complete documentation index at: https://docs.pubrio.com/llms.txt > Use this file to discover all available pages before exploring further. # Daily API Usage > Retrieve a daily breakdown of API requests and credits consumed by the workspace within a date range. The response includes a per-day timeseries and a stacked per-endpoint series suitable for building usage charts. ## OpenAPI ````yaml en-openapi POST /api_keys/usage/daily openapi: 3.0.0 info: description: >- The Pubrio API is used to search, preview and enrich Contacts and Accounts. Pubrio database provides extensive B2B contacts and sales intelligence data. version: 1.0.0 title: Pubrio OpenAPI termsOfService: https://pubrio.com/en/terms-of-service contact: email: king.lai@pubrio.com name: King Lai url: https://pubrio.com/en/get-in-touch license: name: Apache 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://api.pubrio.com security: - pubrio_api_key: [] tags: - name: Profile description: Workspace profile information and usage statistics - name: Enrichment description: Enrich people and company records with detailed B2B data - name: Lookalike description: Find companies similar to a given company - name: Search description: Search for people, companies, jobs, news, and advertisements with filters - name: Lookup description: >- Look up detailed information for specific people, companies, jobs, news, advertisements, and technologies - name: LinkedIn description: Look up people and company data via LinkedIn profile URLs - name: Redeem description: Redeem credits to unlock people contact details (single and batch) - name: Channels description: Manage outreach channel templates (create, update, delete, list) - name: Monitor description: Create and manage data monitors with webhooks, statistics, and processing - name: Filters description: >- Retrieve available filter values for search parameters (technologies, locations, verticals, etc.) - name: API Keys description: List and inspect API request logs and usage analytics for API keys externalDocs: description: >- The Pubrio API is used to search, preview and enrich Contacts and Accounts. Pubrio database provides extensive B2B contacts and sales intelligence data. url: https://docs.pubrio.com paths: /api_keys/usage/daily: post: tags: - API Keys summary: Get daily API usage timeseries description: >- Retrieve a daily breakdown of API requests and credits consumed by the workspace within a date range. The response includes a per-day timeseries and a stacked per-endpoint series suitable for building usage charts. operationId: api_keys_get_usage_daily requestBody: required: true content: application/json: schema: type: object required: - start_date - end_date properties: profile_id: $ref: '#/components/schemas/profile_id' start_date: type: string example: '2026-05-01' description: >- Start of the date range in `YYYY-MM-DD` format (interpreted in the workspace timezone). end_date: type: string example: '2026-05-14' description: >- End of the date range in `YYYY-MM-DD` format (interpreted in the workspace timezone). keys: type: array items: type: string description: >- Optional list of masked API key identifiers (e.g. `0••••••••••••••••f39`) to restrict the results to specific keys. Use the masked values returned by `/api_keys` or by the `masked_authentication` field on a log entry. log_type_slugs: type: array items: type: string description: >- Optional list of log type slugs (e.g. `people_search`, `company_search`, `people_redeem`) to restrict the results to specific endpoints. responses: '200': description: Successful response containing a daily usage timeseries. content: application/json: schema: type: object properties: metadata: type: object properties: filters: type: object description: >- Echo of the request filters used to produce this response, with empty values stripped. additionalProperties: true data: type: object properties: series: type: array description: >- Per-day totals across all endpoints, sorted ascending by date. items: type: object properties: date: type: string description: Day in `YYYY-MM-DD` format. credits: type: number description: Credits consumed on this day. requests: type: integer description: Number of API requests on this day. by_log_type: type: array description: >- Per-endpoint stacked series, ordered by credits then requests (descending). items: type: object properties: slug: type: string description: >- Log type slug. `__unknown__` indicates requests not mapped to a billable log type. name: type: string description: Human-readable log type name. totals: type: object properties: credits: type: number requests: type: integer series: type: array items: type: object properties: date: type: string credits: type: number requests: type: integer totals: type: object properties: credits: type: number requests: type: integer example: metadata: filters: start_date: '2026-05-01' end_date: '2026-05-14' data: series: - date: '2026-05-01' credits: 26352 requests: 2827 - date: '2026-05-05' credits: 798 requests: 402 - date: '2026-05-11' credits: 187 requests: 187 by_log_type: - slug: people_redeem name: Redeem People totals: credits: 40835 requests: 4083 series: - date: '2026-05-01' credits: 26140 requests: 2614 - date: '2026-05-11' credits: 185 requests: 15 - slug: people_search name: People Search totals: credits: 633 requests: 212 series: - date: '2026-05-05' credits: 594 requests: 199 totals: credits: 41892 requests: 4896 '400': $ref: '#/components/responses/general_error' '429': $ref: '#/components/responses/rate_limit_error' '500': $ref: '#/components/responses/server_error' components: schemas: profile_id: type: integer description: >- Optional. An identifier for the user profile (workspace) making the request. This is no longer required as the API key already includes your workspace information. If provided, it helps in associating the lookup with a specific user, allowing for data retrieval and credit tracking. Check out `user details` endpoints under the Profile tab for more information. responses: general_error: description: >- Bad request. The request was malformed or contained invalid parameters. Check the error code and message for details. content: application/json: schema: required: - code - message - details type: object properties: code: example: 40001 type: integer message: example: >- Errors and codes will vary depending on the scenario, please see the documentation for information. type: string details: type: object rate_limit_error: description: >- Rate limit exceeded. Too many requests were made in a given time period. Retry after the rate limit window resets. content: application/json: schema: required: - error type: object properties: error: example: Request rate limit exceeded. Please wait and try again later. type: string server_error: description: >- Internal server error. An unexpected error occurred on the server. Contact support if the error persists. content: application/json: schema: required: - error type: object properties: error: example: An unexpected error occurred on the server. type: string securitySchemes: pubrio_api_key: type: apiKey name: pubrio-api-key description: >- A unique API token that represents the actions you perform through the API and the corresponding permissions and operations. You can create it through the [Settings](https://dashboard.pubrio.com/#/settings/) section. in: header ````