Connect the world's APIs to Web3 with Chainlink Functions. Get started

CBOR Parse Task

CBOR Parse tasks parse a CBOR payload, typically as part of a Direct Request workflow. In Direct Request, a user makes an on-chain request using a ChainlinkClient contract, which encodes the request parameters as CBOR. See below for an example.


  • data: A byte array containing the CBOR payload.
  • mode: An optional parameter that specifies how to parse the incoming CBOR. The default mode is diet, which expects the input to be a map. Set the mode to standard to pass literal values through “as-is”. Empty inputs return nil.


A map containing the request parameters. Parameters can be individually accessed using $(dot.accessors).


// First, we parse the request log and the CBOR payload inside of it
decode_log  [type="ethabidecodelog"
             abi="SomeContractEvent(bytes32 requestID, bytes cborPayload)"]

decode_cbor [type="cborparse"

// Then, we use the decoded request parameters to make an HTTP fetch
fetch [type="http" url="$(decode_cbor.fetchURL)" method=GET]
parse [type="jsonparse" path="$(decode_cbor.jsonPath)" data="$(fetch)"]

// ... etc ...

See the Direct Request page for a more comprehensive example.

Stay updated on the latest Chainlink news