invoicepdfs-com Logs API

The logs API from invoicepdfs-com — 1 operation(s) for logs.

Operations 1

GET /api/v1/logs List Logs #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/invoicepdfs-com:invoicepdfs-com-logs-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

invoicepdfs-com-logs-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Invoicepdfs Com Logs API
  version: 0.3.0
  contact:
    name: InvoicePDFs
    url: https://invoicepdfs.com/
  license:
    name: MIT
  description: 'Operations tagged logs across 2 of this provider''s published API definitions: openapi.json, invoicepdfs-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Logs
paths:
  /api/v1/logs:
    get:
      tags:
      - Logs
      summary: List Logs
      description: 'Recent API requests made with your keys, newest first.


        Method, path, status, duration and the request and response bodies, so you

        can see what an integration actually sent rather than what it meant to.


        Filter to `success` or `error` with `status`. How long these are kept

        depends on the plan — `get_usage_limits` reports the retention.'
      operationId: list_logs
      security:
      - HTTPBearer: []
      parameters:
      - name: status
        in: query
        required: false
        schema:
          type: string
          pattern: ^(success|error)?$
          default: ''
          title: Status
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          maximum: 1000
          minimum: 1
          default: 100
          title: Limit
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiRequestLogsListResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiErrorResponse'
      x-visibility: internal
components:
  schemas:
    ApiRequestLogOut:
      properties:
        id:
          type: string
          title: Id
        method:
          type: string
          title: Method
        path:
          type: string
          title: Path
        query:
          anyOf:
          - type: string
          - type: 'null'
          title: Query
        status_code:
          type: integer
          title: Status Code
        duration_ms:
          anyOf:
          - type: integer
          - type: 'null'
          title: Duration Ms
        request_body:
          anyOf:
          - type: string
          - type: 'null'
          title: Request Body
        response_body:
          anyOf:
          - type: string
          - type: 'null'
          title: Response Body
        created_at:
          type: string
          title: Created At
      type: object
      required:
      - id
      - method
      - path
      - status_code
      - created_at
      title: ApiRequestLogOut
    ApiErrorResponse:
      type: object
      title: ApiErrorResponse
      properties:
        error:
          type: object
          properties:
            status:
              type: integer
              example: 422
              description: HTTP status, mirroring the response status line.
            code:
              type: string
              example: unprocessable_entity
            message:
              type: string
              example: Request validation failed
            request_id:
              type: string
              nullable: true
              description: Trace id for this request; also returned as X-Trace-Id.
            details:
              type: object
              nullable: true
              description: Error-specific context. Validation failures carry `fields`.
          required:
          - status
          - code
          - message
      required:
      - error
    ApiRequestLogsListResponse:
      properties:
        data:
          items:
            $ref: '#/components/schemas/ApiRequestLogOut'
          type: array
          title: Data
      type: object
      required:
      - data
      title: ApiRequestLogsListResponse
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
x-refined-from:
- openapi.json
- invoicepdfs-com-openapi.json
x-internal-tags:
- auth
- jobs
- logs