# callWithoutNop · FT4 TypeScript client · Chromia Docs (concept)

> callWithoutNop(
    connection: Connection ,
    authenticator: Authenticator ,
    ...operations: Operation[],
): Web3PromiEvent< TransactionWithReceipt ,

Source: https://docs.chromia.com/pages/ft4-ts-client/functions/ft-session.callWithoutNop/

Function

# callWithoutNop

* ```signature
  callWithoutNop(
      connection: Connection,
      authenticator: Authenticator,
      ...operations: Operation[],
  ): Web3PromiEvent<
      TransactionWithReceipt,
      { built: SignedTransaction; sent: Buffer },
  >
  ```

  Same as [call](https://docs.chromia.com/pages/ft4-ts-client/functions/ft-session.call/) but does not insert a nop at the end of the transaction.
  This means that subsequent calls to this operation with the same input might fail due to
  a transaction with the same rid already being in the tx history.

  #### Parameters

  + connection: [Connection](https://docs.chromia.com/pages/ft4-ts-client/interfaces/ft-session.Connection/)

    connection to the blockchain which the transaction will be submitted
  + authenticator: [Authenticator](https://docs.chromia.com/pages/ft4-ts-client/interfaces/authentication.Authenticator/)

    authenticator to use when authenticating the operations in the transaction
  + ...operations: Operation[]

    the operations to include in the transaction

  #### Returns Web3PromiEvent<     [TransactionWithReceipt](https://docs.chromia.com/pages/ft4-ts-client/types/transaction-builder.TransactionWithReceipt/),     { built: SignedTransaction; sent: Buffer }, >

  promi-event which will emit once when transaction is built and once when it is sent. It will resolve to a transaction receipt.

[View this page on docs.chromia.com](https://docs.chromia.com/pages/ft4-ts-client/functions/ft-session.callWithoutNop.html)Generated API reference, mirrored from the live docs