---
title: "Seed the ledger from historical documents"
method: POST
path: "/api/v1/ap/seed"
tags: ["AP monitor"]
---

# Seed the ledger from historical documents

`POST /api/v1/ap/seed`

## Request

- Base URL: `https://tamperlens.com` (the document declares no server; this is the origin it was published from)
- URL: `https://tamperlens.com/api/v1/ap/seed`
- Auth: none declared

The cold-start answer: batch-upload the last 12 months of supplier invoices and boletos at onboarding and the ledger is populated on day one. multipart/form-data, up to 25 PDFs per request; call repeatedly for more. **Upload oldest first**: the version chain records coordinate changes in the order documents arrive. Seeded documents record history and raise NO alerts: a legitimate bank change last year is history, not news. Documents are parsed in memory and never stored, whatever the account's retention setting.

## Response `200`

Default Response

- object

## Other responses

- `400`: Default Response
- `401`: Default Response
- `413`: Default Response
- `422`: Default Response
- `429`: Default Response
- `503`: Default Response

---

[API](https://skmtc.dev/tamperlens/apis/tamperlens-api.md) · [All operations](https://skmtc.dev/tamperlens/apis/tamperlens-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tamperlens/apis/tamperlens-api/revisions/e1b7ae64347b?raw)