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

# Mark an information action as read

> Acknowledge that the end-user has read the information message identified by the URL. Both `cue_id` and `secret` are obtained from the action's `resolution_link.url`; the `secret` is a signed token bound to a member and expires 1 hour after it is issued.

Once acknowledged, the cue is marked as done and no longer appears in the device's `actions` list. The body is optional and accepts `location` / `client_info` for tracing.



## OpenAPI

````yaml https://app.podero.com/api/partners/v2.0/openapi.json post /api/partners/v2.0/cues/{resource_id}/information/resolve
openapi: 3.1.0
info:
  title: Podero Partner API
  version: '2.0'
  description: >-
    This API provides a unified interaction point for Podero's partner
    companies.


    The goal of this API is to give partners easily integratable endpoints that
    don't require extensive software

    development. For this reason, the endpoints focus around user and device
    management, setting of preferences

    and high level device controls.


    While direct control of devices is implemented for special use cases such as
    pause power, we abstract away low level

    direct device steering so developers and partners can focus on delivering
    maximum value to end users.
  termsOfService: https://www.podero.com/terms-and-conditions
servers: []
security: []
paths:
  /api/partners/v2.0/cues/{resource_id}/information/resolve:
    post:
      tags:
        - Cues
      summary: Mark an information action as read
      description: >-
        Acknowledge that the end-user has read the information message
        identified by the URL. Both `cue_id` and `secret` are obtained from the
        action's `resolution_link.url`; the `secret` is a signed token bound to
        a member and expires 1 hour after it is issued.


        Once acknowledged, the cue is marked as done and no longer appears in
        the device's `actions` list. The body is optional and accepts `location`
        / `client_info` for tracing.
      operationId: integrations_api_api_v2_cues_router_resolve_information_cue
      parameters:
        - in: path
          name: resource_id
          schema:
            description: The information notification id
            format: uuid
            title: Resource Id
            type: string
          required: true
          description: The information notification id
        - in: query
          name: secret
          schema:
            description: Signed secret authorising the caller
            title: Secret
            type: string
          required: true
          description: Signed secret authorising the caller
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/InformationActionInput'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InformationActionOutput'
      security:
        - OAuth2: []
components:
  schemas:
    InformationActionInput:
      description: >-
        Body shape for resolving an action whose `code` is `information`. The
        body is optional.
      properties:
        location:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: Optional caller location metadata recorded alongside the read event.
          title: Location
        client_info:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: >-
            Optional caller client metadata (user-agent, device, etc.) recorded
            alongside the read event.
          title: Client Info
      title: InformationActionInput
      type: object
    InformationActionOutput:
      description: Response shape for resolving an action whose `code` is `information`.
      properties:
        action_id:
          description: ID of the action whose read was recorded.
          title: Action Id
          type: string
      required:
        - action_id
      title: InformationActionOutput
      type: object
  securitySchemes:
    OAuth2:
      type: oauth2
      flows:
        password:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}
        clientCredentials:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}

````