When I call the upload file api, the parsedTextUrl prop is not in the response (even though it should be, according to the schema https://docs.vapi.ai/api-reference/files/create). I only find it when I use the get file endpoint. I need the parsedTextUrl for non-txt files when uploaded

Hi there! 👋 I understand your frustration with the

parsedTextUrl

property not appearing in the upload file API response despite being in the schema. Unfortunately, I couldn't find specific information explaining why this discrepancy exists. However, I can help you with how to retrieve the

parsedTextUrl

for your non-txt files. Based on the documentation I found, while the

parsedTextUrl

isn't returned in the initial upload response, you can retrieve it using the get file endpoint. Here's how: 1. First, upload your file using the Upload File API (POST

https://api.vapi.ai/file

) 2. From the upload response, note the

id

of your uploaded file 3. Then use the Get File API to retrieve the complete file information including the `parsedTextUrl`: - Method: GET - Endpoint:

https://api.vapi.ai/file/:id

- Path parameters: Replace

:id

with your file's ID - Headers: Include

Auth: Bearer <your_token>

According to the [API documentation](https://docs.vapi.ai/api-reference/files/get), this get file endpoint will return the complete file information including the

parsedTextUrl

property that you need. If you're still experiencing issues, some troubleshooting steps include: - Verifying your API authentication details - Checking network activity and API responses using browser developer tools - Ensuring the content type is set correctly - Reviewing logs for any error messages Is there anything else you'd like to know about retrieving the

parsedTextUrl

or using the Vapi file APIs? Sources: - [API documentation](https://docs.vapi.ai/api-reference/files/get) - [Upload File API](https://docs.vapi.ai/api-reference/files/create)

It is because the file undergoes a processing phase to extract its text content, and the parsedTextUrl becomes accessible only after this processing is complete..

I appreciate the feedback. I think it might be helpful to not add unavailable properties to the response schema.

checking if this is resolved/solved for you?