Get Payment Posting Settings
GET/api/ledger/payment-posting
Returns whether payment posting has started (and from which date), the A/R and A/P true-up that started it, where each payment type's payments land, and where each channel's payouts land.
accounting:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
payment_accounts lists every payment type that has payments: provider_account is the bank account it is mapped to in the accounting provider, ledger_account the same account in SKU.io's chart and via how it was found (provider_account = explicitly linked, provider_account_code = same account code, system_clearing = store credit / gift card clearing). When it cannot be found, ledger_account is null and problem says what to fix: map the payment type to a bank account, or add that bank account to the chart. Nothing is created automatically. problem_count counts those rows; while any exist, payment posting cannot start.
payout_accounts lists each sales channel with payouts in the ledger: deposit_nominal_code_id / deposit_account is the bank account its payout deposits debit (set with PUT /api/integration-instances/{id} and integration_settings.payout_deposit_nominal_code_id), and problem names the fix when none is set. problem_count counts payment-type and payout-channel gaps together.
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.