A 404 response from POST assetdatabases/{webId}/import on PI Web API 2023 SP1 is consistent with the import endpoint having been removed in that release. In this configuration, changing the XML or repeating the request will not restore the missing route.
Root Cause of the Import 404
The documented AssetDatabase import request no longer maps to an available endpoint in PI Web API 2023 SP1. This explains why export can succeed while import returns 404: export success confirms its own route and connection, but it does not confirm that the separate import route exists.
Affected Configuration and Evidence
| Component | Observed version or behavior | Engineering conclusion |
|---|---|---|
| PI Web API | 2023 SP1 | The AssetDatabase import endpoint was removed in this release. |
| AF Server | 2018 SP3 Patch 5 | Imports succeed through other interfaces. |
| Operating system | Windows Server 2019 | No evidence identifies the operating system as the cause. |
| Web API export | Successful | Does not establish availability of the import endpoint. |
| Web API import | HTTP 404 | Consistent with the removed route. |
Select a Supported Import Path
Use an available AF import mechanism instead of the removed PI Web API route. The evidence confirms successful imports through PI System Explorer and AFSDK. The AF Import and Export utility is another documented option to evaluate for workflows that require a utility rather than an interactive or SDK-based process.
- Confirm that the failing server is running PI Web API 2023 SP1.
- Stop treating
assetdatabases/{webId}/importas an available import interface on that release. - Import the XML through PI System Explorer or the existing AFSDK workflow. Evaluate the AF Import and Export utility if it better matches the deployment process.
Verify the Workaround
After selecting an alternate path, import the same XML and confirm that the AF database is created or updated as intended. Successful PI System Explorer or AFSDK import separates the XML and AF Server from the Web API routing problem. If an alternate path also fails, investigate that failure independently rather than attributing it to the removed Web API endpoint.
FAQ
Why does PI Web API 2023 SP1 return 404 for AssetDatabase import?
The assetdatabases/{webId}/import endpoint was removed in PI Web API 2023 SP1, so a POST to that route returns 404 instead of starting an import.
Does successful PI Web API export prove that import should work?
No. Export and import use separate operations; a successful export does not prove that the removed import route is available.
How can I import an AF database when the Web API endpoint is unavailable?
Use PI System Explorer or AFSDK, both of which successfully imported the XML in the reported configuration. The AF Import and Export utility is also an option to evaluate for a utility-based workflow.