API Access to Perplexity Project Context, Files, Memory, and Conversation History

Feature Requests
, ,
1

Summary:
I’d like the Perplexity API to support connecting API calls to an existing Perplexity Project, so API-based workflows can use that Project’s context, instructions, files, memory, and conversation history.

Use case:
I use the Perplexity API with Cursor to automate work across multiple projects. Each project has its own context, files, instructions, and ongoing history, but API calls currently feel separate from those Perplexity Projects.

Requested functionality:

  • Select a Perplexity Project when making an API request
  • Use that Project’s instructions, files, memory, and context in API responses
  • Keep API conversations associated with a specific Project
  • Optionally sync or log API conversations back into the Project
  • Support project-aware workflows for coding, research, and automation tools

Why this matters:
This would help developers keep context organized across multiple projects instead of manually recreating instructions, uploading files again, or losing continuity between Perplexity Projects and API-based tools.

Example workflow:

  1. I create a Perplexity Project for a software project.
  2. I add files, instructions, and relevant context to that Project.
  3. In Cursor, I call the Perplexity API and specify that Project.
  4. The API response uses the Project’s context.
  5. The conversation can optionally be saved back to the Project for future continuity.

Privacy/access expectations:
It would be helpful if this feature respected Project permissions and allowed developers to control whether API conversations are private, visible in the Project, or synced back.

Thanks for considering this feature.

Best Regards,
Avihai Roimi