> ## Documentation Index > Fetch the complete documentation index at: https://docs.neo.projectdiscovery.io/llms.txt > Use this file to discover all available pages before exploring further. # Export issues > Export issues as CSV or JSON. Supports the same filters as list issues, including task_id. JSON responses use a versioned envelope with exported_at, evidence_schema_version defaults, and normalized reproduction_steps for downstream systems. ## OpenAPI ````yaml https://neo.api.projectdiscovery.io/api/openapi.json get /api/v1/issues/export openapi: 3.1.0 info: contact: name: ProjectDiscovery url: https://neo.projectdiscovery.io description: Neo API Server - Security agent orchestration platform license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0 title: Neo API version: 1.0.0 servers: - description: Production url: https://neo.api.projectdiscovery.io - description: Local development url: http://localhost:8080 security: [] tags: - description: Task execution and management name: Tasks - description: Agent listing and management name: Agents - description: Public agent directory name: Agent Directory - description: User file storage management name: Files - description: User working memory management name: Memory - description: Scheduled and recurring task management name: Schedules - description: Knowledge base and semantic search name: Knowledge - description: Encrypted user credentials and API keys name: Secrets - description: Neo API key management for programmatic access name: API Keys - description: User profile and account information name: User - description: Task and LLM usage tracking name: Usage - description: Bring Your Own Key provider management name: BYOK - description: Model discovery and capabilities name: Models - description: Third-party integrations name: Integrations - description: Skill knowledge documents for agent prompts name: Skills - description: Team management and member invitations name: Teams - description: Prompt library management and discovery name: Prompts - description: Slack bot integration for workspace installation and OAuth name: Slack - description: GitHub integration for PR reviews and repository management name: GitHub - description: Vulnerability issue tracking and management name: Issues - description: Subscription billing and plans name: Billing - description: Project management and member assignments name: Projects - description: SSH key pair generation and management for remote server access name: SSH Keys - description: Codebase structural analysis and mapping name: Codemaps - description: AI-generated codebase documentation and security analysis name: CodeWiki - description: Captured HTTP traffic query and replay name: Network Events paths: /api/v1/issues/export: get: tags: - Issues summary: Export issues description: >- Export issues as CSV or JSON. Supports the same filters as list issues, including task_id. JSON responses use a versioned envelope with exported_at, evidence_schema_version defaults, and normalized reproduction_steps for downstream systems. operationId: get-v1-issues-export parameters: - description: Export format in: query name: format required: false schema: default: json enum: - csv - json type: string - description: Exclude raw_data field from JSON export to reduce size in: query name: exclude_raw required: false schema: default: false type: boolean - explode: true in: query name: severity required: false schema: items: $ref: '#/components/schemas/IssueSeverity' type: array style: form - explode: true in: query name: status required: false schema: items: $ref: '#/components/schemas/IssueStatus' type: array style: form - explode: true in: query name: type required: false schema: items: $ref: '#/components/schemas/IssueType' type: array style: form - explode: true in: query name: source required: false schema: items: type: string type: array style: form - in: query name: host required: false schema: type: string - in: query name: search required: false schema: type: string - description: Export only issues with this host in their affected assets in: query name: affected_host required: false schema: type: string - description: Export only issues with at least this many affected assets in: query name: min_affected required: false schema: type: integer - description: Filter issues that contain this CVE ID in: query name: cve_id required: false schema: type: string - description: Filter issues that contain this CWE ID in: query name: cwe_id required: false schema: type: string - description: Filter issues with CVSS score >= this value in: query name: min_cvss required: false schema: format: float type: number - description: Filter issues with CVSS score <= this value in: query name: max_cvss required: false schema: format: float type: number - description: Export only issues belonging to this project in: query name: project_id required: false schema: format: uuid type: string - description: Export only issues associated with this task ID in: query name: task_id required: false schema: type: string responses: '200': content: application/json: schema: format: binary type: string text/csv: schema: format: binary type: string description: Exported issues file '500': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Internal server error components: schemas: IssueSeverity: enum: - critical - high - medium - low - info - unknown type: string IssueStatus: enum: - unverified - open - confirmed - in_progress - resolved - false_positive - accepted_risk - duplicate type: string IssueType: enum: - vulnerability - misconfiguration - exposure - information - compliance - other type: string ErrorResponse: properties: code: description: > Stable machine-readable error code — branch on this rather than matching the human `error`/`message` strings. Domain codes include `user_spending_cap_reached`, `project_spending_cap_reached`, and `insufficient_neo_credits`; otherwise it mirrors the error kind (e.g. `forbidden`, `invalid_request`, `not_exists`, `already_exists`). example: user_spending_cap_reached type: string error: example: Bad request type: string error_id: description: Correlation id for a specific error instance, when present. type: string kind: description: Coarse error category (e.g. "forbidden request", "invalid request"). example: forbidden request type: string message: description: | Human-readable detail (the kind prefixed to the error). For display, not for branching. type: string required: - error type: object ````