Payments API · fictional product
Ledgerly’s API reference is generated from OpenAPI and complete to the field — and developers still asked basic questions in their community channel. They imported the reference and guides by sitemap, kept one knowledge base per API version, and bound the centered search to ⌘K across the docs site.
Centered search on the docs
Real answers from their sources, with the citations a customer sees.
How do I make a payment request safe to retry?
Send an Idempotency-Key header with a unique value on the POST; repeated requests with the same key return the original response for 24 hours 1. Keys are scoped to your API key and endpoint 2.
Idempotent requests
API reference · Requests
Provide an Idempotency-Key header to safely retry a request.
Authentication
API reference · Keys
What does error 409 payment_already_captured mean?
The payment was captured by an earlier request, so a second capture is refused 1. Fetch the payment to read its current status instead of retrying the capture 2.
Error codes
Article · Payments errors
Capturing payments
Guide · section 2
Not in the docs
“Do webhooks retry if my endpoint returns 500?”
The answer existed only in a support macro. Uploading the macro as an article closed the gap.
<script
src="https://pagetruth.com/widget.js"
data-key="pk_ledgerly_8f2c1a"
data-layout="modal"
async
></script>The same knowledge base, published at docs.ledgerly.dev for customers who start from search.
Point PageTruth at your docs, publish a help center and drop the widget into your app. The free plan is enough to see it answer your own questions.