Skip to content

send_direct_message

send_direct_message(
    client_id: ClientId,
    topic: Topic,
    *,
    config_overrides: Optional[IoTDataPlaneClientConfig] = None,
    content_type: Optional[ContentType] = None,
    response_topic: Optional[ResponseTopic] = None,
    confirmation: Optional[Confirmation] = None,
    timeout: Optional[TimeoutInSeconds] = None,
    payload: Optional[Payload] = None,
    user_properties: Optional[SynthesizedJsonUserProperties] = None,
    payload_format_indicator: Optional[PayloadFormatIndicator] = None,
    correlation_data: Optional[CorrelationData] = None,
) -> SendDirectMessageResponse

Sends an MQTT message directly to a specific client identified by its client ID.

SendDirectMessage targets a single client ID. The receiving client does not need to subscribe to the topic, but the receiver's policy must allow iot:Receive on the specified topic.

Requires permission to access the SendDirectMessage action.

For more information about messaging costs, see Amazon Web Services IoT Core pricing.

Parameters:

  • client_id (ClientId) –

    The unique identifier of the MQTT client to send the message to.

    Client IDs must not exceed 128 characters and can't start with a dollar sign ($). MQTT client IDs must be URL encoded (percent-encoded) when they contain characters that are not valid in HTTP requests, such as spaces, forward slashes (/), and UTF-8 characters. For more information, see Amazon Web Services IoT Core message broker and protocol limits and quotas.

  • topic (Topic) –

    The topic of the outbound MQTT Publish message to the receiving client. For more information, see Amazon Web Services IoT Core message broker and protocol limits and quotas.

  • content_type (Optional[ContentType], default: None ) –

    The MQTT5 content type property forwarded to the receiving client (for example, application/json).

  • response_topic (Optional[ResponseTopic], default: None ) –

    A UTF-8 encoded string that's used as the topic name for a response message. The response topic describes the topic which the receiver should publish to as part of the request-response flow. The topic must not contain wildcard characters. For more information, see Amazon Web Services IoT Core message broker and protocol limits and quotas.

  • confirmation (Optional[Confirmation], default: None ) –

    A Boolean value that specifies whether to wait for delivery confirmation from the receiving client.

    When set to true, the API delivers the message at QoS 1 and waits for the client to send a delivery confirmation (PUBACK) before returning a successful response. If delivery confirmation is not received within the specified timeout period, the API returns HTTP 504.

    When set to false, the API delivers the message at QoS 0 and returns after Amazon Web Services IoT Core attempts to deliver the message.

    Valid values: true | false

    Default value: false

  • timeout (Optional[TimeoutInSeconds], default: None ) –

    An integer that represents the maximum time, in seconds, to wait for a delivery confirmation (PUBACK) from the receiving client after the message has been delivered. This parameter is only used when confirmation is set to true. If confirmation is false, this parameter is ignored.

    The total API response time may be higher than this value due to internal processing. Set your HTTP client timeout to a value greater than this parameter.

    Valid range: 1 to 15 seconds.

    Default value: 5 seconds.

  • payload (Optional[Payload], default: None ) –

    The message body. MQTT accepts text, binary, and empty (null) message payloads.

  • user_properties (Optional[SynthesizedJsonUserProperties], default: None ) –

    A JSON string that contains an array of JSON objects. If you don't use Amazon Web Services SDK or CLI, you must encode the JSON string to base64 format before adding it to the HTTP header. userProperties is an HTTP header value in the API.

    For MQTT 3.1.1 clients, user properties are silently dropped.

    The following example userProperties parameter is a JSON string which represents two User Properties. Note that it needs to be base64-encoded:

    [{"deviceName": "alpha"}, {"deviceCnt": "45"}]

  • payload_format_indicator (Optional[PayloadFormatIndicator], default: None ) –

    An Enum string value that indicates whether the payload is formatted as UTF-8. payloadFormatIndicator is an HTTP header value in the API.

  • correlation_data (Optional[CorrelationData], default: None ) –

    The base64-encoded binary data used by the sender of the request message to identify which request the response message is for when it's received. correlationData is an HTTP header value in the API.

Raises:

Source code in docs_src/capo_iot_data_plane/_services/io_t_data_plane.py
def send_direct_message(
    self,
    client_id: "capo_iot_data_plane.types.client_id.ClientId",
    topic: "capo_iot_data_plane.types.topic.Topic",
    *,
    config_overrides: Optional[IoTDataPlaneClientConfig] = None,
    content_type: Optional[
        "capo_iot_data_plane.types.content_type.ContentType"
    ] = None,
    response_topic: Optional[
        "capo_iot_data_plane.types.response_topic.ResponseTopic"
    ] = None,
    confirmation: Optional[
        "capo_iot_data_plane.types.confirmation.Confirmation"
    ] = None,
    timeout: Optional[
        "capo_iot_data_plane.types.timeout_in_seconds.TimeoutInSeconds"
    ] = None,
    payload: Optional["capo_iot_data_plane.types.payload.Payload"] = None,
    user_properties: Optional[
        "capo_iot_data_plane.types.synthesized_json_user_properties.SynthesizedJsonUserProperties"
    ] = None,
    payload_format_indicator: Optional[
        "capo_iot_data_plane.types.payload_format_indicator.PayloadFormatIndicator"
    ] = None,
    correlation_data: Optional[
        "capo_iot_data_plane.types.correlation_data.CorrelationData"
    ] = None,
) -> "capo_iot_data_plane.types.send_direct_message_response.SendDirectMessageResponse":
    """<p>Sends an MQTT message directly to a specific client identified by its client ID.</p> <p> <code>SendDirectMessage</code> targets a single client ID. The receiving client does not need to subscribe to the topic, but the receiver's policy must allow <code>iot:Receive</code> on the specified topic.</p> <p>Requires permission to access the <a href="https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsiot.html#awsiot-actions-as-permissions">SendDirectMessage</a> action.</p> <p>For more information about messaging costs, see <a href="http://aws.amazon.com/iot-core/pricing/">Amazon Web Services IoT Core pricing</a>.</p>

    Args:
        client_id: <p>The unique identifier of the MQTT client to send the message to.</p> <p>Client IDs must not exceed 128 characters and can't start with a dollar sign ($). MQTT client IDs must be URL encoded (percent-encoded) when they contain characters that are not valid in HTTP requests, such as spaces, forward slashes (/), and UTF-8 characters. For more information, see <a href="https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits">Amazon Web Services IoT Core message broker and protocol limits and quotas</a>.</p>
        topic: <p>The topic of the outbound MQTT Publish message to the receiving client. For more information, see <a href="https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits">Amazon Web Services IoT Core message broker and protocol limits and quotas</a>.</p>
        content_type: <p>The MQTT5 content type property forwarded to the receiving client (for example, <code>application/json</code>).</p>
        response_topic: <p>A UTF-8 encoded string that's used as the topic name for a response message. The response topic describes the topic which the receiver should publish to as part of the request-response flow. The topic must not contain wildcard characters. For more information, see <a href="https://docs.aws.amazon.com/general/latest/gr/iot-core.html#message-broker-limits">Amazon Web Services IoT Core message broker and protocol limits and quotas</a>.</p>
        confirmation: <p>A Boolean value that specifies whether to wait for delivery confirmation from the receiving client.</p> <p>When set to <code>true</code>, the API delivers the message at QoS 1 and waits for the client to send a delivery confirmation (PUBACK) before returning a successful response. If delivery confirmation is not received within the specified <code>timeout</code> period, the API returns HTTP 504.</p> <p>When set to <code>false</code>, the API delivers the message at QoS 0 and returns after Amazon Web Services IoT Core attempts to deliver the message.</p> <p>Valid values: <code>true</code> | <code>false</code> </p> <p>Default value: <code>false</code> </p>
        timeout: <p>An integer that represents the maximum time, in seconds, to wait for a delivery confirmation (PUBACK) from the receiving client after the message has been delivered. This parameter is only used when <code>confirmation</code> is set to <code>true</code>. If <code>confirmation</code> is <code>false</code>, this parameter is ignored.</p> <p>The total API response time may be higher than this value due to internal processing. Set your HTTP client timeout to a value greater than this parameter.</p> <p>Valid range: 1 to 15 seconds.</p> <p>Default value: <code>5</code> seconds.</p>
        payload: <p>The message body. MQTT accepts text, binary, and empty (null) message payloads.</p>
        user_properties: <p>A JSON string that contains an array of JSON objects. If you don't use Amazon Web Services SDK or CLI, you must encode the JSON string to base64 format before adding it to the HTTP header. <code>userProperties</code> is an HTTP header value in the API.</p> <p>For MQTT 3.1.1 clients, user properties are silently dropped.</p> <p>The following example <code>userProperties</code> parameter is a JSON string which represents two User Properties. Note that it needs to be base64-encoded:</p> <p> <code>[{"deviceName": "alpha"}, {"deviceCnt": "45"}]</code> </p>
        payload_format_indicator: <p>An <code>Enum</code> string value that indicates whether the payload is formatted as UTF-8. <code>payloadFormatIndicator</code> is an HTTP header value in the API.</p>
        correlation_data: <p>The base64-encoded binary data used by the sender of the request message to identify which request the response message is for when it's received. <code>correlationData</code> is an HTTP header value in the API.</p>

    Raises:
        capo_iot_data_plane.errors.forbidden_exception.ForbiddenException: <p>The caller isn't authorized to make the request.</p>
        capo_iot_data_plane.errors.gateway_timeout_exception.GatewayTimeoutException: <p>The delivery confirmation was not received from the client within the specified timeout period.</p>
        capo_iot_data_plane.errors.internal_failure_exception.InternalFailureException: <p>An unexpected error has occurred.</p>
        capo_iot_data_plane.errors.invalid_request_exception.InvalidRequestException: <p>The request is not valid.</p>
        capo_iot_data_plane.errors.request_entity_too_large_exception.RequestEntityTooLargeException: <p>The payload exceeds the maximum size allowed.</p>
        capo_iot_data_plane.errors.resource_not_found_exception.ResourceNotFoundException: <p>The specified resource does not exist.</p>
        capo_iot_data_plane.errors.throttling_exception.ThrottlingException: <p>The rate exceeds the limit.</p>
        capo_iot_data_plane.errors.unauthorized_exception.UnauthorizedException: <p>You are not authorized to perform this operation.</p>
        capo_iot_data_plane.errors.UnknownServiceError: The service returned an error code this client does not model.
    """

    def _handler(
        req: "OperationRequest[capo_iot_data_plane.types.send_direct_message_request.SendDirectMessageRequest]",
    ) -> OperationResponse[
        "capo_iot_data_plane.types.send_direct_message_response.SendDirectMessageResponse"
    ]:
        import capo_iot_data_plane._operations.iot_moonraker_service.send_direct_message

        output, http_response = (
            capo_iot_data_plane._operations.iot_moonraker_service.send_direct_message.send_direct_message(
                req.options, req.input
            )
        )
        return OperationResponse(output=output, response=http_response)

    interceptors_, options_ = self.operation_options(
        config_overrides, OperationLogging("SendDirectMessage")
    )
    input_: capo_iot_data_plane.types.send_direct_message_request.SendDirectMessageRequest = {
        "client_id": client_id,
        "topic": topic,
    }
    if content_type is not None:
        input_["content_type"] = content_type
    if response_topic is not None:
        input_["response_topic"] = response_topic
    if confirmation is not None:
        input_["confirmation"] = confirmation
    if timeout is not None:
        input_["timeout"] = timeout
    if payload is not None:
        input_["payload"] = payload
    if user_properties is not None:
        input_["user_properties"] = user_properties
    if payload_format_indicator is not None:
        input_["payload_format_indicator"] = payload_format_indicator
    if correlation_data is not None:
        input_["correlation_data"] = correlation_data

    response = execute_pipeline(
        OperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    response.response.close()
    return response.output