You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The data returned from calling the API should match the same privacy and masking policies applied to it as it does if the query is performed on the app or on the website.
🔍 Problem Statement
The data returned from API/curl today is masked for sensitive information such as name, email, some URL's (LinkedIn), etc. The same query on the web or app returns unmasked data. This presents a problem for automating tasks via API which it's suppose to solve.
💡 Proposed Solution
Implement the same masking policy for both web and app and API data returned.
📌 API Impact
Which API component is affected? Returned data from all API endpoints as far as I can tell
Is this related to a specific model? All models
Would this require new API parameters or changes to existing ones? hopefully not
🔄 Alternatives Considered
Alternative is to scrape the perplexity web interface and look for returned data that is unmasked. It's not ideal and counter intuitive to using API.
🚀 Feature Request
The data returned from calling the API should match the same privacy and masking policies applied to it as it does if the query is performed on the app or on the website.
🔍 Problem Statement
The data returned from API/curl today is masked for sensitive information such as name, email, some URL's (LinkedIn), etc. The same query on the web or app returns unmasked data. This presents a problem for automating tasks via API which it's suppose to solve.
💡 Proposed Solution
Implement the same masking policy for both web and app and API data returned.
📌 API Impact
🔄 Alternatives Considered
Alternative is to scrape the perplexity web interface and look for returned data that is unmasked. It's not ideal and counter intuitive to using API.
📎 Additional Context
none
📧 For direct inquiries, please reach out to api@perplexity.ai
The text was updated successfully, but these errors were encountered: