Docs

Get Global Issues CSV

gethttps://app.fossa.com/api/v2/issues/csv/global

Download the global issues report bundle (a zip of per-category issue-list CSVs and/or a counts CSV) or submit it for background processing. The counts CSV differs by scope: team/organization scope yields `issue_counts.csv`, a daily time series, while a release-group scope yields `release_counts.csv`, a release-indexed comparison series. Requires the `Create` permission on either `OrganizationReport` or `TeamReport`; requests from users without one of these permissions are rejected with a `403`.

Query parameters

emailboolean

When `true`, we will submit the report for background processing and deliver via email when ready. Otherwise the report will be streamed via API

teamIdsstring | string[] | enum

Scope the report to one or more team IDs. Accepts a single team ID, an array of team IDs, or the literal string `"null"`. Invalid (non-integer) team IDs are rejected with a `400`. Ignored for organizations on the free tier.

releaseGroupIdinteger

Scope the issue-list export to a single release group, using its latest release (the issues shown on the release group's Issues page). Requires view access to the release group; otherwise rejected with a `403`. When set, `teamIds` is ignored — the export is scoped to the release group only, not an intersection of both filters. When combined with `includeDailyCounts`, the bundle's counts CSV is `release_counts.csv` rather than the daily `issue_counts.csv`.

includeIssuesListboolean

Whether to include the per-category issue-list CSVs in the bundle. Defaults to `true` when omitted. Setting this to `false` without `includeDailyCounts=true` selects no reports and is rejected with a `400`.

includeDailyCountsboolean

Whether to include a counts CSV in the bundle. Defaults to `false`. For team/organization scope this is `issue_counts.csv`, a daily time series of active, ignored, and remediated counts. When `releaseGroupId` is set it is instead `release_counts.csv`, holding one row per release (New / Remediated / Unchanged versus the previous release), capped at the 10 most recent scanned releases.

Responses

200CSV report (as a zip file) or background task metadata
idinteger

Unique identifier for the task

taskstring

Name of the task being run

jobTokenstring

Token used to poll for the task's status and result

statusenum

Current status of the task

CREATEDASSIGNEDRUNNINGSUCCEEDEDFAILED
attempt_numberinteger

Number of times the task has been attempted

maxRetriesinteger | null

Maximum number of retries permitted for the task

startedstring | null <date-time>

When the task started running, or null if it has not started

finishedstring | null <date-time>

When the task finished, or null if it has not finished

scheduledStartTimestring | null <date-time>

When the task is scheduled to start, or null

podstring | null

Identifier of the pod running the task, or null

contextobject

Task-specific context payload

createdAtstring <date-time>

When the task record was created

updatedAtstring <date-time>

When the task record was last updated

400Bad Request
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

403Forbidden
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

500Server Error
uuidstring

Unique identifier associated with the error

codeinteger

fossa specific error code

messagestring

message associated with this error

namestring

name of the error

httpStatusCodeinteger

http status code number

Try this endpoint

Build a request and run it against app.fossa.com.

Bearer

Stored in this browser for 24 hours. Try It uses a docs proxy for CORS and does not store tokens server-side.

GET https://app.fossa.com/api/v2/issues/csv/global
curl --request GET \  --url 'https://app.fossa.com/api/v2/issues/csv/global' \  --header 'accept: application/json' \  --header 'authorization: Bearer YOUR_API_TOKEN'

Real request. Mutating methods can change data.

Click Try It to run a request and see the response here.
Enter a Bearer token before running this request.

Query params

emailboolean

When `true`, we will submit the report for background processing and deliver via email when ready. Otherwise the report will be streamed via API

teamIdsstring

Scope the report to one or more team IDs. Accepts a single team ID, an array of team IDs, or the literal string `"null"`. Invalid (non-integer) team IDs are rejected with a `400`. Ignored for organizations on the free tier.

releaseGroupIdinteger

Scope the issue-list export to a single release group, using its latest release (the issues shown on the release group's Issues page). Requires view access to the release group; otherwise rejected with a `403`. When set, `teamIds` is ignored — the export is scoped to the release group only, not an intersection of both filters. When combined with `includeDailyCounts`, the bundle's counts CSV is `release_counts.csv` rather than the daily `issue_counts.csv`.

includeIssuesListboolean

Whether to include the per-category issue-list CSVs in the bundle. Defaults to `true` when omitted. Setting this to `false` without `includeDailyCounts=true` selects no reports and is rejected with a `400`.

includeDailyCountsboolean

Whether to include a counts CSV in the bundle. Defaults to `false`. For team/organization scope this is `issue_counts.csv`, a daily time series of active, ignored, and remediated counts. When `releaseGroupId` is set it is instead `release_counts.csv`, holding one row per release (New / Remediated / Unchanged versus the previous release), capped at the 10 most recent scanned releases.

← All Issues endpoints