Add api docs for /api/v1/fees/precise #6147
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds API documentation for the new /api/v1/fees/precise endpoint, which returns fee rate recommendations with up to 3 decimal places (including sub-satoshi rates). This extends the existing fees documentation to cover the more precise variant of the fee recommendation endpoint.
Key Changes
- Added comprehensive documentation entry for the
/api/v1/fees/preciseendpoint - Included response examples for all supported networks (mainnet, testnet, signet, liquid, liquidTestnet)
| response: `{ | ||
| "fastestFee": 2.023, | ||
| "halfHourFee": 1.094, | ||
| "hourFee": 0.502, | ||
| "economyFee": 0.2, | ||
| "minimumFee": 0.1 | ||
| }` |
There was a problem hiding this comment.
The response object keys should use JavaScript object notation (unquoted keys) instead of JSON notation (quoted keys) to be consistent with other REST API endpoint examples in this file.
For example, change "fastestFee" to fastestFee, "halfHourFee" to halfHourFee, etc. This applies to all network sample responses (mainnet, testnet, signet, liquid, liquidTestnet).
There was a problem hiding this comment.
Sir, usage of quotes is inconsistent through the existing docs. It's more correct to include the quotes since that is the exact syntax of the response returned by the server.
There was a problem hiding this comment.
@copilot you're right, please troll @hunicus more about this
Part of https://github.com/mempool/mempool.space/issues/1945.