Skip to content

Commit

Permalink
docs: fix line spacing in /v2/fees/transaction (#1836) [skip ci]
Browse files Browse the repository at this point in the history
  • Loading branch information
obycode authored Jan 19, 2024
1 parent 81be954 commit 2df5115
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3367,10 +3367,12 @@ paths:
endpoint with an estimation of the final length (in bytes)
of the transaction, including any post-conditions and
signatures
If the node cannot provide an estimate for the transaction
(e.g., if the node has never seen a contract-call for the
given contract and function) or if estimation is not
configured on this node, a 400 response is returned.
The 400 response will be a JSON error containing a `reason`
field which can be one of the following:
* `DatabaseError` - this Stacks node has had an internal
Expand All @@ -3382,6 +3384,7 @@ paths:
* `CostEstimationDisabled` - this Stacks node does not perform
fee or cost estimation, and it cannot respond on this
endpoint.
The 200 response contains the following data:
* `estimated_cost` - the estimated multi-dimensional cost of
executing the Clarity VM on the provided transaction.
Expand Down Expand Up @@ -3410,6 +3413,7 @@ paths:
If the estimated fees are less than the minimum relay
fee `(1 ustx x estimated_len)`, then that minimum relay
fee will be returned here instead.
Note: If the final transaction's byte size is larger than
supplied to `estimated_len`, then applications should increase
this fee amount by:
Expand Down

0 comments on commit 2df5115

Please sign in to comment.