How to specify different kinds of pay expr in the same parallel reduce (non network token and algo)

[alcyoneus-g]

  .api(
      BuyerApi.touch,
      () => {},
      () => 0,
      (k) => {
        k(null);
        return [
            balance(token),  
        ];
      }
    )
    .api(
      BuyerApi.reveal,
      () => {
        assume(lastConsensusSecs() > end, "reveal time hasn't been reached")
      },
      () => [[1, token]],
      (k) => {

I keep getting this issue:

reachc: error[RE0088]: These types are mismatched:
  expected: UInt
       got: Tuple(Tuple(UInt, Token))

  ./index.rsh:179:73:block app

there are some APIs that require algo payments and some require a token transfer, how to handle those without this issue?

[jeapostrophe]

This is what .paySpec is for --- https://docs.reach.sh/rsh/step/#p_32 --- you need to include everything everywhere and Reach will optimize away things that are 0

[alcyoneus-g]

@jeapostrophe but what I want to achieve is that some APIs use ALGO as payment (that's why the first api is just 0 instead of tuple of tuple), and some api use the tokens like the second one.

Something like:

 .api(
      BuyerApi.api1,
      () => {},
      () => 1000000,
      (k) => {
        k(null);
        return [
        ];
      }
    )
    .api(
      BuyerApi.api2
      () => {},
      () => [[1, token]],
      (k) => {

[jeapostrophe]

That's what my solution would let you do.

[alcyoneus-g]

so, I get how it would work for 0 but how would I go about expressing () => 1000000, ?

() => [100000, [0, token]] is correct?

[jeapostrophe]

Yup

[alcyoneus-g]

thanks for the help @jeapostrophe, it's has worked 👍