> ## 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.

# Report the outcome of an active action

> Report the outcome of an action previously started via `/cues/{cue_id}/resolve`. Requires the same signed `secret` used to start it. The action must still be active — otherwise a 404 is returned.

- `state=success` marks the action as completed; it will no longer appear in the   originating resource's `actions` list on subsequent reads.
- `state=fail` records the failure but leaves the action available, so the caller   can retry by calling `/resolve` again.



## OpenAPI

````yaml https://app.podero.com/api/partners/v2.0/openapi.json post /api/partners/v2.0/cues/{cue_id}/state
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/{cue_id}/state:
    post:
      tags:
        - Cues
      summary: Report the outcome of an active action
      description: >-
        Report the outcome of an action previously started via
        `/cues/{cue_id}/resolve`. Requires the same signed `secret` used to
        start it. The action must still be active — otherwise a 404 is returned.


        - `state=success` marks the action as completed; it will no longer
        appear in the   originating resource's `actions` list on subsequent
        reads.

        - `state=fail` records the failure but leaves the action available, so
        the caller   can retry by calling `/resolve` again.
      operationId: integrations_api_api_v2_cues_router_report_cue_state
      parameters:
        - in: path
          name: cue_id
          schema:
            description: The action's ID
            format: uuid
            title: Cue Id
            type: string
          required: true
          description: The action's ID
        - in: query
          name: secret
          schema:
            description: Signed secret authorising the caller for this action
            title: Secret
            type: string
          required: true
          description: Signed secret authorising the caller for this action
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CueStateInput'
        required: true
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CueStateOutput'
components:
  schemas:
    CueStateInput:
      properties:
        state:
          description: >-
            Outcome of the action: `success` marks it completed, `fail` records
            a failure and leaves it available to retry.
          enum:
            - success
            - fail
          title: State
          type: string
        payload:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: >-
            Optional free-form payload forwarded to the action handler (e.g.
            provider-specific result data).
          title: Payload
        location:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: >-
            Optional caller location metadata recorded alongside the outcome
            event.
          title: Location
        client_info:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: >-
            Optional caller client metadata (user-agent, device, etc.) recorded
            alongside the outcome event.
          title: Client Info
      required:
        - state
      title: CueStateInput
      type: object
    CueStateOutput:
      properties:
        action_id:
          description: ID of the action whose outcome was recorded.
          title: Action Id
          type: string
      required:
        - action_id
      title: CueStateOutput
      type: object

````