Create Entry Despite Suspected Duplicate
POST/api/ledger/entries/:entry/create-despite-duplicate
"Not a duplicate — create anyway" for an entry the pre-push duplicate check held back as a suspected duplicate (its latest sync operation is needs_action with error_payload.reason = duplicate_suspected). Records your ruling that the matched provider document is a different document, then queues a fresh push that creates a NEW document. The existing provider document is left untouched.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The ruling applies to the matched document only: if a different provider document matches this entry later, the entry is held back again.
Authentication: Requires Bearer token.
Request body:
reason(string, required, max 1000) — why this is not a duplicate. Kept on the entry as the audit record (who, when, why, and the provider document dismissed), visible in the entry's operation transitions (decision) and inGET /api/ledger/entries/{entry}/sync-inspection→duplicate_dismissals.
Refusals (422, data.create_despite_duplicate.reason):
not_duplicate_suspected— the entry is not held back as a suspected duplicatealready_linked— the entry is already linked to a provider documententry_withdrawn— the entry was reversed or discardedperiod_locked— the entry is dated in a locked period (SKU's lock or the provider's lock date)ineligible— another push rule refuses it;reasonslists the codes (e.g.batch_member,before_provider_sync_start_date,connection_inactive)
A missing or blank reason returns a standard 422 validation error.
Response: 200 with data.create_despite_duplicate (created, connection_id, operation_id of the queued push) and data.entry (the refreshed ledger entry).
Permission: requires accounting.sync. Returns 403 without it; 404 when the entry does not exist.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 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.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Entity
Response Headers
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.