Inventory Manager API · sources
The organization's legacy sources
GET /sources
The organization's legacy sources — the platforms it is migrating from (an ERP or inventory system it is leaving), whatever app provides each: its type (a slug the app declares), the app that provides it, where the migration stands (connected, importing, mirroring, retired), when the first import landed (importedAt) and what it brought, per kind (counts).
Live sources first, then by name. What the onboarding walk and Settings read to say what an import covered.
Access
Requires imports:read or integrations:read or setup:read.
Any one of these scopes is enough.
How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.
AI agent tool
Agents call this as inventory_list_sources (Inventory: List sources), in the imports toolset. It only reads.
Connecting an agent: AI agents.
Example
curl -X GET 'https://inventory.getmanifold.io/sources' \
-H "Authorization: Bearer $MANIFOLD_TOKEN"const response = await fetch("https://inventory.getmanifold.io/sources", {
method: "GET",
headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();{
"items": [
{
"sourceId": "src_019cb5dc-bf88-756c-8d01-2fa61dd4b669",
"appId": "app_019b8b74-1fd0-7d77-ba23-1c91bb26607d",
"type": "legacy-erp",
"name": "Previous ERP",
"status": "mirroring",
"importedAt": "2026-03-04T01:12:40.000Z",
"counts": [
{
"kind": "products",
"count": 412
},
{
"kind": "locations",
"count": 2
},
{
"kind": "parties",
"count": 1380
},
{
"kind": "stock-positions",
"count": 824
}
],
"connectedAt": "2026-03-03T22:41:09.000Z",
"updatedAt": "2026-03-04T01:12:40.000Z"
}
]
}The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web
page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: inventory-manager.openapi.json. Base URL https://inventory.getmanifold.io.
Errors
Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.
401
| Refusal | What it means | What to do |
|---|---|---|
Unauthorized reason | The token is missing, expired or not one Manifold issued. | Get a fresh token and send the call again. |
TokenAlreadyUsed tokenId | A single-use app token was already spent. | Mint a new token for this call. |
402
| Refusal | What it means | What to do |
|---|---|---|
SubscriptionRequired status | The organization's subscription has lapsed, so writes are refused. | An owner settles billing. Reads still work meanwhile. |
403
| Refusal | What it means | What to do |
|---|---|---|
TenantRequired userId | The token names no organization. | Choose the organization, then get a new token. |
ScopeRequired required | The token's roles do not grant the scope this call needs. | Ask an owner or admin for a role that grants it. |
409
| Refusal | What it means | What to do |
|---|---|---|
MirroredFromSource source | This area is fed by your source system until the organization goes live. | Make the change in the source system, or go live first. |
503
| Refusal | What it means | What to do |
|---|---|---|
RequestLogUnavailable tokenId, reason | The service could not record the request, so it did nothing. | Try again shortly. |
How refusals work everywhere: Errors.