Overview
Once you have uploaded a positions file to Data Adapter, the service runs through all assets and processes only those that pass file validation. Assets that fail validation are dropped within Data Adapter.
To track the progress of your upload and diagnose why certain assets were dropped, you can utilise the v3 API endpoints. These endpoints completely replace the deprecated v2 task status tracking endpoint (GET/v2/task/:taskID/status).
Error Resolution Process
To identify, review, and fix validation errors in your position file, follow these steps:
Check Your File Upload Status
Make a GET request to the Positions Status (v3) endpoint to see the overall processing state of your file.
URL: https://{environment_name}-api.fundapps.co/v3/data/positions/{id}/status
Review the status field, which will display InProgress, Success, Failed, Cancelled, or UnexpectedError.
If the payload returns "hasWarnings": true or a Failed status, errors or warnings occurred during the data enrichment process.
Retrieve Specific Error Messages
If your upload status flags an issue, call the Positions Messages (v3) endpoint to extract the precise reasons your assets were dropped.
URL: https://{environment_name}-api.fundapps.co/v3/data/positions/{id}/messages
This returns a detailed list that includes the severity level (Warning or Error) and the explicit message content (e.g., missing instrument classification schemes or data provider extraction errors).
Correct Your CSV Position File
After reviewing the error messages returned by the GET request, please correct them in your CSV position file accordingly.
Our Data Adapter Shareholding Disclosure and Position Limits property specifications are helpful resources for correcting the required properties.
If you want to review your data provider package (Refinitiv or Bloomberg) to ensure you have the correct data packages, please see this link.
Additional Troubleshooting Notes
When interacting with the v3 endpoints, ensure your requests conform to the following technical and security requirements:
Authentication: These APIs require Basic Authentication. You must supply a valid username and password in your request header.
Guid Validation (400 Bad Request): If you receive a 400 error, double-check that the
{id}provided in the URL path parameters is a valid Guid.Credentials (401 Unauthorized): Providing invalid or missing credentials in the header will result in a 401 Unauthorized response.
User Permissions (403 Forbidden): If you receive a 403 error, verify that your user profile has been granted the necessary permissions to upload positions.