---
title: "RecvPacket defines a rpc handler method for MsgRecvPacket."
method: POST
path: "/ibc.core.channel.v1.Msg/RecvPacket"
tags: ["Msg"]
---

# RecvPacket defines a rpc handler method for MsgRecvPacket.

`POST /ibc.core.channel.v1.Msg/RecvPacket`

## Request body

- IbcCoreChannelV1MsgRecvPacket
  - `packet` IbcCoreChannelV1Packet
    - `data` string, byte
    - `destination_channel` string — identifies the channel end on the receiving chain.
    - `destination_port` string — identifies the port on the receiving chain.
    - `sequence` string, uint64 — number corresponds to the order of sends and receives, where a Packet with an earlier sequence number must be sent and received before a Packet with a later sequence number.
    - `source_channel` string — identifies the channel end on the sending chain.
    - `source_port` string — identifies the port on the sending chain.
    - `timeout_height` IbcCoreClientV1Height — Normally the RevisionHeight is incremented at each height while keeping RevisionNumber the same. However some consensus algorithms may choose to reset the height in certain conditions e.g. hard forks, state-machine breaking changes In these cases, the RevisionNumber is incremented so that height continues to be monitonically increasing even as the RevisionHeight gets reset
      - `revision_height` string, uint64
      - `revision_number` string, uint64
    - `timeout_timestamp` string, uint64
  - `proof_commitment` string, byte
  - `proof_height` IbcCoreClientV1Height — Normally the RevisionHeight is incremented at each height while keeping RevisionNumber the same. However some consensus algorithms may choose to reset the height in certain conditions e.g. hard forks, state-machine breaking changes In these cases, the RevisionNumber is incremented so that height continues to be monitonically increasing even as the RevisionHeight gets reset
    - `revision_height` string, uint64
    - `revision_number` string, uint64
  - `signer` string

## Response `200`

A successful response.

- IbcCoreChannelV1MsgRecvPacketResponse — MsgRecvPacketResponse defines the Msg/RecvPacket response type.
  - `result` 'RESPONSE_RESULT_TYPE_UNSPECIFIED' | 'RESPONSE_RESULT_TYPE_NOOP' | 'RESPONSE_RESULT_TYPE_SUCCESS' | 'RESPONSE_RESULT_TYPE_FAILURE' — - RESPONSE_RESULT_TYPE_UNSPECIFIED: Default zero value enumeration - RESPONSE_RESULT_TYPE_NOOP: The message did not call the IBC application callbacks (because, for example, the packet had already been relayed) - RESPONSE_RESULT_TYPE_SUCCESS: The message was executed successfully - RESPONSE_RESULT_TYPE_FAILURE: The message was executed unsuccessfully

## Other responses

- `default` — An unexpected error response.

## Changes

- **2024-08-14** `21c607e4fa20` — 1 info
  - endpoint added
- **2024-07-31** `19416a3f0cd1` — 1 breaking
  - api path removed without deprecation
- **2024-07-11** `ca7e84576c8e` — 1 info
  - endpoint added
- **2024-05-15** `41fb8b09e244` — 1 breaking
  - api path removed without deprecation
- **2024-02-23** `54713b4a9d25` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/pokt-network/apis/http-api-console/changes/ibc.core.channel.v1.Msg/RecvPacket/post.md)

---

[API](https://skmtc.dev/pokt-network/apis/http-api-console.md) · [All operations](https://skmtc.dev/pokt-network/apis/http-api-console/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pokt-network/http-api-console/revisions/de0653d8a73d/schema)