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

# Create an action from an Audit finding

> Creates an accepted action from one finding of a completed audit run in this project, as Create action on the Audit page does: the same action, finding evidence and target pages. Take auditRunId and findingId from List Audit findings. title defaults to the finding's remediation summary. The action is made as the member who created the API key or holds the OAuth grant; they must be a project member with project management permission (403 otherwise). A finding already linked to an open action, from an earlier call, the Audit page or an earlier audit of the same site, returns that action with created false instead of making a second one: its finding evidence and target pages are refreshed, its title changes only when title is sent, and its description stays as stored. A refusal is a 409 and nothing is written. Its reason says why: stale_audit_run (a newer completed audit of the same site exists, or the finding's action was already refreshed from a newer audit, such as another path's audit of the same host for a crawler-access finding; details.latestAuditRunId names the newer run, so read its findings and retry with that id); finding_dismissed (restore the finding with Dismiss or restore an Audit finding first); page_locked (a page the finding affects is locked); acknowledgment_required (a page the finding affects is high-stakes; retry with acknowledgeHighStakes true once a human has confirmed the change, which is recorded on the action and kept when the action is returned later); action_not_open (the finding's action is archived, completed or out of the queue; details.actionId names it, and Change an action status restores or reopens it); retrieval_restriction_acknowledged (every page a crawler-access finding affects is acknowledged as an intentional restriction; reconsider those pages with Acknowledge or reconsider a retrieval restriction first). A crawler-access finding whose audit holds no retrieval evidence, or a stored finding DevTune cannot read, is also a 409. An audit run that is not in this project or did not complete successfully, or a finding id the run does not hold, is a 404. Archive or restore the action with Change an action status. A new action sends an action.created webhook; a returned one sends action.updated. Requires the `actions.write` scope.



## OpenAPI

````yaml /openapi.json post /projects/{projectId}/audit/findings/action
openapi: 3.1.0
info:
  title: DevTune API
  version: 2.0.0
  description: >-
    API for programmatic access to your AI visibility data, webhook
    subscriptions, and automation workflows. Use this API to integrate DevTune
    data into CI/CD pipelines, BI tools, AI agents, and operational systems.
servers:
  - url: https://devtune.ai/api/v2
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Connection and usage
    description: >-
      The project a credential is bound to, its scopes and features, usage, and
      code-mode receipts.
  - name: Setup
    description: >-
      Brands, domains, brand terms, platforms, content sources and pausing a
      project.
  - name: Prompts and topics
    description: Tracked prompts, their topics, and prompt-set analysis.
  - name: Visibility
    description: >-
      Visibility metrics, AI answers, sentiment, competitive position and the
      project timeline.
  - name: Citations
    description: >-
      Citation statistics, the most-cited domains and pages, and cited lookalike
      sites.
  - name: Positioning
    description: How well AI answers match your positioning statements.
  - name: Accuracy
    description: Claims AI answers make about your brand, and contradictions.
  - name: Content gaps
    description: Topics, sources and brands where competitors are cited.
  - name: AI Traffic
    description: >-
      AI referrals, answer fetches, crawls, 404 Demand, Direct lift and Search
      Console totals.
  - name: Adoption
    description: npm downloads and GitHub stars for project domains.
  - name: Audit and pages
    description: Audit findings, Google eligibility, page metrics, and locked pages.
  - name: Actions
    description: Suggested and accepted work, briefs, drafts and pull requests.
  - name: Results
    description: Content changes, measured results and what works.
  - name: Agents
    description: Managed agents, their schedules and runs.
  - name: Dex
    description: Private Dex conversations, specialist handoffs and memory.
  - name: Agent Picks
    description: Agent Picks setup, tests, schedules and results.
  - name: Library and Knowledge
    description: Library items and the Knowledge Profile.
  - name: Webhooks
    description: Webhook subscriptions and signing secrets.
  - name: Agent registration
    description: Setup drafts for an unclaimed agent registration.
paths:
  /projects/{projectId}/audit/findings/action:
    post:
      tags:
        - Audit and pages
      summary: Create an action from an Audit finding
      description: >-
        Creates an accepted action from one finding of a completed audit run in
        this project, as Create action on the Audit page does: the same action,
        finding evidence and target pages. Take auditRunId and findingId from
        List Audit findings. title defaults to the finding's remediation
        summary. The action is made as the member who created the API key or
        holds the OAuth grant; they must be a project member with project
        management permission (403 otherwise). A finding already linked to an
        open action, from an earlier call, the Audit page or an earlier audit of
        the same site, returns that action with created false instead of making
        a second one: its finding evidence and target pages are refreshed, its
        title changes only when title is sent, and its description stays as
        stored. A refusal is a 409 and nothing is written. Its reason says why:
        stale_audit_run (a newer completed audit of the same site exists, or the
        finding's action was already refreshed from a newer audit, such as
        another path's audit of the same host for a crawler-access finding;
        details.latestAuditRunId names the newer run, so read its findings and
        retry with that id); finding_dismissed (restore the finding with Dismiss
        or restore an Audit finding first); page_locked (a page the finding
        affects is locked); acknowledgment_required (a page the finding affects
        is high-stakes; retry with acknowledgeHighStakes true once a human has
        confirmed the change, which is recorded on the action and kept when the
        action is returned later); action_not_open (the finding's action is
        archived, completed or out of the queue; details.actionId names it, and
        Change an action status restores or reopens it);
        retrieval_restriction_acknowledged (every page a crawler-access finding
        affects is acknowledged as an intentional restriction; reconsider those
        pages with Acknowledge or reconsider a retrieval restriction first). A
        crawler-access finding whose audit holds no retrieval evidence, or a
        stored finding DevTune cannot read, is also a 409. An audit run that is
        not in this project or did not complete successfully, or a finding id
        the run does not hold, is a 404. Archive or restore the action with
        Change an action status. A new action sends an action.created webhook; a
        returned one sends action.updated. Requires the `actions.write` scope.
      operationId: createActionFromAuditFinding
      parameters:
        - name: projectId
          in: path
          required: true
          description: >-
            The project the credential is bound to. Read it from GET
            /connection.
          schema:
            type: string
            format: uuid
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: false
              required:
                - auditRunId
                - findingId
              properties:
                acknowledgeHighStakes:
                  type: boolean
                  description: >-
                    True once a human has confirmed creating an action on a
                    high-stakes page the finding affects.
                auditRunId:
                  type: string
                  format: uuid
                findingId:
                  type: string
                  minLength: 1
                  maxLength: 200
                title:
                  type: string
                  minLength: 1
                  maxLength: 500
      responses:
        '200':
          description: >-
            The action linked to the finding, and whether this request created
            it
          content:
            application/json:
              schema:
                type: object
                required:
                  - data
                  - meta
                properties:
                  data:
                    type: object
                    required:
                      - actionId
                      - auditRunId
                      - created
                      - findingId
                    properties:
                      actionId:
                        type: string
                        format: uuid
                      auditRunId:
                        type: string
                        format: uuid
                      created:
                        type: boolean
                      findingId:
                        type: string
                  meta:
                    $ref: '#/components/schemas/Meta'
        '400':
          $ref: '#/components/responses/BadRequestError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '404':
          $ref: '#/components/responses/NotFoundError'
        '409':
          $ref: '#/components/responses/ConflictError'
        '429':
          $ref: '#/components/responses/RateLimitExceededError'
      security:
        - bearerAuth: []
        - oauthBearer: []
components:
  schemas:
    Meta:
      type: object
      description: Sent beside data on every successful response that returns data.
      properties:
        timestamp:
          type: string
          format: date-time
          description: When the response was produced.
        projectId:
          type: string
          format: uuid
    Error:
      type: object
      properties:
        error:
          type: string
          description: >-
            Machine-readable error code, such as bad_request, unauthorized,
            forbidden, not_found, conflict, payment_required,
            rate_limit_exceeded or internal_error. Some endpoints return their
            own codes, listed in their descriptions.
        message:
          type: string
          description: >-
            What went wrong, for a person to read. Do not parse it; use error
            and reason.
        reason:
          type: string
          description: >-
            Why the request was refused, for an error with more than one cause,
            such as a refused content-draft start.
        details:
          type: object
          additionalProperties: true
          description: >-
            Machine-readable facts about the failure or refusal, such as
            retryable or shortfall_credits.
          properties:
            retryable:
              type: boolean
              description: >-
                Read this field before retrying. Present on every 5xx and 429
                response: true when another attempt may succeed, false for a
                permanent refusal even on a 5xx. Other refusals may also provide
                this field.
            retryAfterSeconds:
              type: integer
              minimum: 1
              description: >-
                Seconds to wait when retryable is true on a 429 or 503 response,
                also sent in Retry-After. Uses the provider retry time or
                limiter reset when available; otherwise 60 seconds for 429 and
                GitHub throttles or 30 seconds for other 503 responses. GitHub
                secondary limits wait at least 60 seconds.
        status:
          type: integer
          description: The HTTP status code, repeated in the body.
      required:
        - error
        - message
        - status
  responses:
    BadRequestError:
      description: >-
        The request is invalid: a parameter or body field is missing, has the
        wrong type or is out of range, or a cursor doesn't match this list. The
        message says which; reason, where present, is listed in the endpoint's
        description. Fix the request before retrying, and restart a list without
        its cursor. See [Errors](/api-reference/errors).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    UnauthorizedError:
      description: >-
        The request has no valid credential: the Authorization header is missing
        or malformed, or the API key or OAuth token is invalid, expired or
        revoked. Send `Authorization: Bearer <API key>` with an active key, or
        sign in again to get a new OAuth token. See
        [Errors](/api-reference/errors).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ForbiddenError:
      description: >-
        The credential is valid but can't make this request. The message says
        which cause applies: the key or sign-in lacks the scope this endpoint
        requires (named in the message), it belongs to another project, the plan
        doesn't include API access or this feature, the project is paused (a
        paused project keeps only read scopes and setup.write), or the member a
        write acts as no longer has the role it needs. Read `GET
        /projects/{projectId}/connection` for the credential's current scopes
        and features, then use a key that has the scope, sign in again and
        approve it, or upgrade the plan. See [Errors](/api-reference/errors).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFoundError:
      description: >-
        The resource doesn't exist in this project, was deleted, or the
        credential can't see it. Check the IDs in the path, and that the
        projectId is the project the credential is bound to. See
        [Errors](/api-reference/errors).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    ConflictError:
      description: >-
        The request conflicts with the resource's current state. The message,
        and reason where present, say what conflicts; the endpoint's description
        lists its reasons. Read the resource again, then change the request.
        When the body has retryable true, send the same request again. See
        [Errors](/api-reference/errors).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    RateLimitExceededError:
      description: >-
        Too many requests from this credential in the current window. The
        request was refused before it took effect, so it is safe to retry: wait
        the seconds in Retry-After, then send it again. Endpoints that start
        agent runs have a stricter limit. See [Rate
        limits](/api-reference/rate-limits).
      headers:
        Retry-After:
          description: Seconds to wait before retrying a 429 or retryable 503 response.
          schema:
            type: integer
            minimum: 1
        X-RateLimit-Limit:
          $ref: '#/components/headers/X-RateLimit-Limit'
        X-RateLimit-Remaining:
          $ref: '#/components/headers/X-RateLimit-Remaining'
        X-RateLimit-Reset:
          $ref: '#/components/headers/X-RateLimit-Reset'
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  headers:
    X-RateLimit-Limit:
      description: Maximum requests per window
      schema:
        type: integer
    X-RateLimit-Remaining:
      description: Requests remaining in current window
      schema:
        type: integer
    X-RateLimit-Reset:
      description: Unix timestamp when the window resets
      schema:
        type: integer
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key with dtk_live_ prefix. Obtain it from API Keys in the account
        sidebar. New keys start with all supported scopes selected for the
        chosen project, and you can narrow them to specific read/write scopes as
        needed.
    oauthBearer:
      type: http
      scheme: bearer
      description: >-
        Project-granted OAuth access token from the authorization server
        advertised at /.well-known/oauth-protected-resource/api/v2. Uses the
        same browser consent and current project permissions as MCP. Only
        operations explicitly listing oauthBearer accept these tokens.

````

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