JSON Feed

What is a JSON Feed Back to top

A JSON feed provides structured, machine-readable access to your Jira calendar data. Unlike ICS feeds (designed for calendar applications like Google Calendar and Outlook), JSON feeds are designed for developers and automation.

Use JSON feeds to build custom dashboards, power automation workflows, feed data into third-party integrations, or populate internal tools with live calendar information. The response is a standard JSON object containing calendar metadata and an array of events with configurable fields.

Prerequisites Back to top

A Jira administrator must enable the "Enable Embed and JSON export" toggle in Admin Settings → Export Settings
You must have calendar admin permission on the calendar you want to export

If the "Enable Embed and JSON export" toggle is disabled, the JSON export option will not appear in the Export Settings dialog. Ask your Jira administrator to enable it.

Generate a JSON Feed URL Back to top

Find the calendar you want to export in the left sidebar
Click the edit icon (pencil) next to the calendar name
Select Export Settings from the dropdown menu
Locate the JSON card
Configure Fields to include in the response (these determine what appears in each event's fields object)
Select a Period (how far back and forward to include events)
Click Generate URL
Copy the generated URL

Response Format Back to top

The JSON feed returns a structured response with calendar metadata and an array of events. Each event includes core properties (id, type, title, start, end, allDay) plus a fields object containing the additional fields you selected when generating the URL.

{
  "calendar": { "name": "Sprint Calendar", "id": "cal-123" },
  "generatedAt": "2026-04-03T08:43:05.987Z",
  "events": [
    {
      "id": "PROJ-123",
      "type": "jira",
      "title": "PROJ-123: Fix login bug",
      "start": "2026-04-01",
      "end": "2026-04-02",
      "allDay": true,
      "fields": {
        "status": "In Progress",
        "key": "PROJ-123",
        "summary": "Fix login bug"
      }
    }
  ]
}

The type field indicates whether the event originates from a Jira issue ("jira") or is a custom event ("custom"). The fields object content varies depending on the columns you selected during URL generation.

Options Back to top

Option	Description
Fields	Determines which properties appear in each event's `fields` object. Choose from issue fields (Status, Priority, Assignee, Reporter, Labels, Components, etc.) and event fields (Participants, Description, Link).
Period	Controls the time window of events returned. Options range from 1 month to 2 years. Events outside this window are not included in the response.

Usage Back to top

Fetch the JSON feed using any HTTP client. The URL contains an embedded authentication token, so no additional headers are required.

curl "https://your-site.atlassian.net/x/your-feed-path?token=abc123"

Parse the response as standard JSON in your language of choice (JavaScript, Python, Go, etc.).

CORS Note Back to top

Browser cross-origin requests are blocked. You cannot fetch the JSON feed directly from client-side JavaScript running on an external domain (e.g., fetch() from your website). Use a server-side request instead (Node.js, Python, PHP, etc.) to retrieve the data and serve it to your frontend.

Integration Ideas Back to top

Custom dashboards — pull calendar data into internal dashboards built with React, Vue, or any frontend framework via a backend proxy
Slack / Teams notifications — schedule a script to fetch upcoming events and post daily summaries to team channels
Data warehousing — periodically ingest calendar events into your data warehouse for cross-project reporting and analytics
CI/CD calendar checks — query the calendar before deployments to check for freeze windows or scheduled maintenance