> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchski-attract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List captured query parameters

> One row per query parameter of every matching page view, newest first: e.g. `?key=gclid&from=2026-07-01` lists every Google click ID with its visitor.

The same filters as the page-view list; `key` and `group` apply to each parameter.

**Access:** an API key with `request-log:params:read`, or `ads:all`, or `admin:all`, or a signed-in user holding the `request-log:view` permission. Other callers get 404.

**Rate limit:** the key’s own reads-per-minute limit, set when the key is created (default 600); over it, 429 with `Retry-After`.



## OpenAPI

````yaml /api-reference/openapi.yaml get /request-log/params
openapi: 3.1.0
info:
  title: Fetchski Attract CMS API
  description: >-
    Auto-generated OpenAPI spec for this Fetchski site instance. Authenticate
    machine-to-machine requests with an API key by sending the header
    `Authorization: ApiKey <token>`. Keys are issued in the CMS (API Keys) and
    carry scopes that limit them to specific actions. Each key also has its own
    security policy, chosen when it is created: a signing mode (token only,
    signed writes, or every request signed with the key’s signing secret via
    `X-Fetchski-Timestamp` + `X-Fetchski-Signature`), an optional network
    allowlist, and reads/writes-per-minute limits (429 with `Retry-After` over
    them). Some routes require a signature from every key — see each route.
  version: 1.0.0
servers:
  - url: https://{host}/api/v1
    description: 'Your site: set `host` to its host name.'
    variables:
      host:
        default: acme.example
security: []
tags:
  - name: Authentication
    description: >-
      Sign in as a person to get a bearer token or a session cookie.
      Integrations use an API key instead: send `Authorization: ApiKey <token>`.
  - name: SDK Packages
    description: >-
      The site’s own npm registry and Composer repository for the Attract SDKs,
      so an app installs them with one of the site’s API keys. Point npm, pnpm,
      Bun or Composer at them; the SDKs never call them.
  - name: Pages
    description: 'The page tree: each page’s content, place and URL.'
  - name: Global Content
    description: Site-wide content and settings every page shares.
  - name: Redirects
    description: Old URLs and where they now send visitors.
  - name: Internationalization
    description: The site’s locales.
  - name: Languages
    description: >-
      The site’s languages: the main language’s name and every further
      language’s name, code and Public switch. A save applies at once: a new
      language gets its home page and its own addresses (/fr/…), and its pages
      are then translated with each type’s localize routes.
  - name: Page Templates
    description: >-
      The site’s whole-page starting arrangements. They are not pages of the
      site (the Pages list leaves them out for API keys): read one, then make a
      page from it with Pages → create and `_copyingId` (`copyingId` in the
      SDKs).
  - name: Blog Posts
    description: The blog’s posts, and importing them from Markdown or MDX.
  - name: Blog Categories
    description: The categories posts are filed under.
  - name: Authors
    description: The people posts are credited to.
  - name: Team Members
    description: The people the Team section shows.
  - name: Testimonials
    description: Quotes from customers.
  - name: FAQ Items
    description: Questions and their answers.
  - name: FAQ Categories
    description: The groups questions are sorted into.
  - name: Google Reviews
    description: Reviews from the business’s Google profile, synced on a schedule.
  - name: Instagram Posts
    description: Posts from the connected Instagram account, synced on a schedule.
  - name: Service Areas
    description: The places the business serves, for the service map.
  - name: Cookies
    description: The cookies the consent banner declares.
  - name: Media
    description: The Images and Files libraries, and their tags.
  - name: Videos
    description: The Videos library.
  - name: Image Folders
    description: The folders that organize the Images library.
  - name: File Folders
    description: The folders that organize the Files library.
  - name: Video Folders
    description: The folders that organize the Videos library.
  - name: Photo Albums
    description: Hand-picked, ordered sets of photos for galleries.
  - name: Photo Feeds
    description: >-
      Feeds that collect photos from a connected photo source into the Images
      library on a schedule.
  - name: Attachments
    description: Uploading files and cropping images.
  - name: Fetchski Media
    description: >-
      Read-only discovery over the Images and Videos libraries: find what to
      reference in an MDX blog import, or which file to use, with its URLs.
  - name: Forms
    description: The site’s forms and their fields.
  - name: Form Submissions
    description: >-
      What visitors sent through the site’s forms. Submissions hold personal
      details: give a key `forms:read` only where it is needed.
  - name: Conversion Events
    description: >-
      The conversion event log — one record per conversion, with its attribution
      and consent snapshot and its delivery to each ad platform. Read it
      incrementally, post facts from other systems (a reservation purchase, a
      lead outcome), and adjust them (refunds, cancellations). One event ID
      travels everywhere as the platforms’ de-duplication key.
  - name: Visitor Attribution
    description: >-
      Per-visitor attribution on this site: first touch, last ad or campaign
      touch, and the ad platforms’ browser IDs. The join other systems use to
      attach a purchase to the marketing-site journey that led to it.
  - name: Ads Metrics
    description: >-
      Aggregates for dashboards: ad-click landings and conversions, by day,
      platform, campaign and more.
  - name: Conversions
    description: >-
      Conversion definitions — the visitor actions (a lead, a call click, a
      booking, a purchase) this site reports to the ad platforms, each with a
      row per platform. Managed by administrators in the CMS.
  - name: Webhooks
    description: >-
      Push notifications of form submissions and conversion-event changes to the
      site’s Webhook Destinations — signed with each destination’s own secret,
      retried for a day, at-least-once. Set destinations up in the CMS (Webhook
      Destinations, for people granted “Manage webhook destinations”): URL,
      events, optional filters and custom headers, and the signing secret shown
      once.
  - name: Request Log
    description: >-
      The page views the site captured (Connections → Tracking → Request log),
      and the query parameters on them: campaign tags and ad click IDs.
paths:
  /request-log/params:
    get:
      tags:
        - Request Log
      summary: List captured query parameters
      description: >-
        One row per query parameter of every matching page view, newest first:
        e.g. `?key=gclid&from=2026-07-01` lists every Google click ID with its
        visitor.


        The same filters as the page-view list; `key` and `group` apply to each
        parameter.


        **Access:** an API key with `request-log:params:read`, or `ads:all`, or
        `admin:all`, or a signed-in user holding the `request-log:view`
        permission. Other callers get 404.


        **Rate limit:** the key’s own reads-per-minute limit, set when the key
        is created (default 600); over it, 429 with `Retry-After`.
      operationId: listRequestLogParams
      parameters:
        - name: from
          in: query
          required: false
          description: Captured at or after this ISO 8601 date or date-time.
          schema:
            type: string
            format: date-time
        - name: to
          in: query
          required: false
          description: Captured at or before this ISO 8601 date or date-time.
          schema:
            type: string
            format: date-time
        - name: pathPrefix
          in: query
          required: false
          description: Only paths starting with this, e.g. `/blog`.
          schema:
            type: string
        - name: visitorId
          in: query
          required: false
          description: Only this visitor (the `fetchski_vid` UUID).
          schema:
            type: string
        - name: country
          in: query
          required: false
          description: Only this two-letter country code, e.g. `US`.
          schema:
            type: string
            pattern: ^[A-Za-z]{2}$
        - name: status
          in: query
          required: false
          description: Only this HTTP status, e.g. `404`.
          schema:
            type: integer
            minimum: 100
        - name: notFound
          in: query
          required: false
          description: Only page views that did (`true`) or did not (`false`) find a page.
          schema:
            type: boolean
        - name: group
          in: query
          required: false
          description: Only rows with a parameter in this group, e.g. `ads` or `utm`.
          schema:
            type: string
        - name: key
          in: query
          required: false
          description: >-
            Only rows with this query parameter (case-insensitive), e.g.
            `gclid`.
          schema:
            type: string
        - name: paramKey
          in: query
          required: false
          description: The same as `key` (`paramKey` wins when both are sent).
          schema:
            type: string
        - name: page
          in: query
          required: false
          description: Page number, from 1 (a page past the end answers the last page).
          schema:
            type: integer
            minimum: 1
            default: 1
        - name: perPage
          in: query
          required: false
          description: Rows per page.
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 25
      responses:
        '200':
          description: A page of query parameters.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RequestLogParamPage'
        '401':
          $ref: '#/components/responses/KeyedUnauthorized'
        '403':
          $ref: '#/components/responses/KeyedForbidden'
        '404':
          $ref: '#/components/responses/KeyedNotFound'
        '429':
          $ref: '#/components/responses/KeyedRateLimited'
      security:
        - ApiKeyAuth:
            - request-log:params:read
      x-codeSamples:
        - lang: typescript
          label: TypeScript
          source: >-
            import { createSiteClient } from '@fetchski/attract-cms-sdk';


            const site = createSiteClient();

            const requestLogParamPage = await
            site.requestLog().listRequestLogParams();
        - lang: php
          label: Laravel
          source: >-
            use Fetchski\AttractCmsLaravel\Facades\Attract;


            $requestLogParamPage =
            Attract::requestLog()->listRequestLogParams();
components:
  schemas:
    RequestLogParamPage:
      type: object
      description: A page of query parameters.
      required:
        - params
        - total
        - page
        - perPage
        - totalPages
      properties:
        params:
          type: array
          items:
            $ref: '#/components/schemas/RequestLogParamRow'
        total:
          type: integer
          description: Every match, across all pages.
        page:
          type: integer
        perPage:
          type: integer
        totalPages:
          type: integer
          minimum: 1
    RequestLogParamRow:
      type: object
      description: One query parameter of one captured page view.
      required:
        - requestId
        - createdAt
        - key
        - value
        - group
        - path
        - url
        - visitorId
        - country
        - referrer
      properties:
        requestId:
          type: string
          description: The page view’s `_id`.
        createdAt:
          type: string
          format: date-time
        key:
          type: string
        value:
          type: string
        group:
          type:
            - string
            - 'null'
          description: The group a classification rule put it in.
        path:
          type: string
        url:
          type: string
        visitorId:
          type:
            - string
            - 'null'
          description: Set only with Analytics or Marketing consent.
        country:
          type:
            - string
            - 'null'
          description: Two-letter country code.
        referrer:
          type:
            - string
            - 'null'
          description: Origin + path with consent, origin only without.
    KeyedError:
      type: object
      description: >-
        Every refusal: the error kind, a message saying what to fix, and
        details.
      required:
        - name
        - message
      properties:
        name:
          type: string
          description: The error kind, e.g. `forbidden`.
        message:
          type: string
        data:
          type: object
          additionalProperties: true
  responses:
    KeyedUnauthorized:
      description: >-
        The API key is missing, malformed, unknown, disabled, expired or
        archived, or a request its signing mode requires to be signed is not.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/KeyedError'
          example:
            name: invalid
            message: The API key is not valid.
            data: {}
    KeyedForbidden:
      description: >-
        The API key lacks the scope this route needs (the message names it) or
        is used from outside its allowlist; or, on a route that answers 403 to
        everyone it refuses, the caller may not use it.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/KeyedError'
          example:
            name: forbidden
            message: 'This API key lacks the required scope: forms:read.'
            data: {}
    KeyedNotFound:
      description: >-
        Nothing matches the identifier, or the caller may not use this route at
        all (it is not advertised).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/KeyedError'
          example:
            name: notfound
            message: Not found.
            data: {}
    KeyedRateLimited:
      description: The key used up its per-minute limit. Wait `Retry-After` seconds.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/KeyedError'
          example:
            name: tooManyRequests
            message: This API key’s rate limit is used up for this minute.
            data: {}
      headers:
        Retry-After:
          description: Seconds until the budget resets.
          schema:
            type: integer
            minimum: 1
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Paste your API key as the CMS showed it: `fsk_<site>_<key id>_<secret>`
        (issued under API Keys). `ApiKey ` in front of it works too. Leave it
        empty to read as the public.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.