PyCharm

Before opening Bubble, clarify what you actually want to connect. If your goal is to display project data — issues, code review status, deployment history — from your JetBrains development workflow inside a Bubble app, you want Path 1: the JetBrains Space REST API. Space is the hosted DevOps platform JetBrains ships with PyCharm Professional and Team subscriptions, and it has a documented REST API at https://{org}.jetbrains.space/api/http. No Python code required for this path. If your goal is for Bubble to call custom business logic — data transformations, ML models, file processing, third-party API orchestration that Bubble can't do natively — you want Path 2: build and deploy a Python service in PyCharm (Flask or FastAPI are the most beginner-friendly), then configure the Bubble API Connector to call that service's HTTPS URL. This tutorial walks through Path 1 in full detail (the Space API), then covers what changes for Path 2 in the final step. Non-technical founders should follow Path 1. Founders with a developer available should consider Path 2 for complex Bubble apps.

For Path 1, you need a Service Application token from JetBrains Space — this is safer than a Personal Token because it grants only the scopes your Bubble app needs, and it doesn't expire when a team member leaves. In your browser, go to your JetBrains Space organization: https://{org}.jetbrains.space. Click the gear icon in the top-right corner to open Administration. In the left sidebar, find Applications under the 'Authentication' section and click it. Click New Application in the top-right. Give it a name like 'Bubble Integration' and click Create. On the application's page, go to the Authorization tab. Click Configure Requirements. Add the following permissions based on what your Bubble app will display: - Projects → Project.Issues.View (to read issues) - Projects → Deployments.View (to read deployment status) - Projects → CodeReview.View (to read code review status) Click Save. Now go to the Permanent Tokens tab and click Generate Token. Copy the token immediately — it won't be shown again. Store it somewhere safe like a password manager. This token goes into Bubble's API Connector as a Private header, so it never touches the browser.

Open your Bubble app editor. In the left sidebar, click the Plugins tab (the puzzle piece icon). If you don't see the API Connector in your installed plugins list, click Add plugins, search for 'API Connector', find the one published by Bubble, and click Install. Return to the Plugins tab. Click API Connector in the installed plugins list. Click Add another API to create a new API group. In the 'API Name' field, enter 'JetBrains Space'. In the 'Shared headers for all calls' section, click Add a shared header. Set the key to `Authorization` and the value to `Bearer YOUR_TOKEN_HERE` — replace `YOUR_TOKEN_HERE` with the token you copied in the previous step. Critically, check the 'Private' checkbox to the right of this header. This tells Bubble to process this header server-side only, so the token never appears in the user's browser network tab. In the 'Base URL' field (if available at the API level) or in each call, you will use: `https://{org}.jetbrains.space/api/http` Replace `{org}` with your actual JetBrains Space organization subdomain. If your Space URL is myteam.jetbrains.space, the base URL is https://myteam.jetbrains.space/api/http. Using just jetbrains.space without your org subdomain will return a 404 error.

1{
2  "API Name": "JetBrains Space",
3  "Authentication": "None or Private Key in Header",
4  "Shared Headers": {
5    "Authorization": "Bearer <private>"
6  },
7  "Base URL": "https://{org}.jetbrains.space/api/http"
8}

With the JetBrains Space API group configured, click Add another call inside it to define your first endpoint. For listing issues in a project: - Set the call name to 'Get Project Issues' - Set the method to GET - Set the URL to: `https://{org}.jetbrains.space/api/http/projects/id:{projectKey}/issues` - Replace `{org}` with your Space subdomain and `{projectKey}` with your project's key (found in Space under the project → Settings → General) - In the 'Parameters' section, add a parameter named `$top` with a value of `50` (limits results to 50 issues at a time, avoiding large payloads) - Set 'Use as' to 'Data' Click Initialize call. Bubble will make a live request to Space with your credentials. You need a real successful response for initialization to work — if your project has no issues, create a test issue in Space first. Once Bubble shows the response, it auto-detects fields like `id`, `title`, `status`, `assignee`, and `createdAt`. Click Save. For triggering a deployment (optional, for POST calls): - Add another call named 'Trigger Deployment' - Set method to POST - URL: `https://{org}.jetbrains.space/api/http/applications/{appId}/deployments/trigger` - Add a JSON body parameter for the deployment payload - Set 'Use as' to 'Action' Note: if the Initialize call returns 'There was an issue setting up your call', check that your Space token has the correct permission scope for that endpoint and that you're using the correct org subdomain.

1GET https://{org}.jetbrains.space/api/http/projects/id:{projectKey}/issues
2Headers:
3  Authorization: Bearer <private>
4Query Params:
5  $top: 50
6  $skip: 0
7
8Example response structure:
9{
10  "data": [
11    {
12      "id": "PROJ-1",
13      "title": "Fix login page layout",
14      "status": { "name": "Open" },
15      "assignee": { "name": "Jane Doe" },
16      "createdAt": "2026-06-01T10:00:00Z"
17    }
18  ],
19  "next": "50"
20}

Now connect the API data to a Bubble UI. Go to the Design tab and open (or create) the page where you want to display Space issues. From the UI Components panel, drag a Repeating Group onto the canvas. In the Repeating Group's property panel on the right, set: - Type of content: 'JetBrains Space Get Project Issues' (this is the Data Type Bubble created from your initialized call) - Data source: Click 'Get data from an external API', select 'JetBrains Space - Get Project Issues', and fill in your `projectKey` parameter Inside the Repeating Group's first cell (Bubble only lets you design the first cell — it repeats automatically), add text elements bound to the API fields: - Title text: Set 'Insert dynamic data' → Current cell's JetBrains Space Get Project Issues → title - Status text: Current cell's → status → name - Assignee text: Current cell's → assignee → name To avoid loading too many issues at once (Bubble's Repeating Group works best with under 100 items), use the `$top` parameter to limit results to 25-50. If you need pagination, add 'Previous' and 'Next' buttons that change the `$skip` value using a custom state. For the 'Trigger Deployment' call, add a Button element. Create a Workflow triggered by the button click. Add the action 'Plugins → JetBrains Space - Trigger Deployment' and fill in the required parameters. This gives non-technical team members a safe 'Deploy' button without any terminal access. If you are building Path 2 (calling your own Python backend instead), skip the Space-specific data binding and instead point a GET or POST call at your deployed FastAPI/Flask HTTPS endpoint. The API Connector setup is identical — just a different base URL and auth method matching your backend.

If your Bubble app stores Space issue data in the database (for example, caching issues or saving user interactions like 'approved' status), you must configure Privacy Rules to prevent unauthorized data access. Go to the Data tab in your Bubble editor. Click Privacy in the left sidebar. For each data type that stores Space-derived data, click 'Define rules for {Type}'. By default in Bubble, data is accessible to anyone — this is a common security gap. Add a rule: 'When: Current User is logged in → Allow: Find this {Type}, View all fields'. Remove the 'Everyone else' rule if it grants too broad access. Also consider Workload Unit (WU) costs: every API Connector call in a Bubble Workflow costs approximately 1 WU. If your dashboard runs Space API calls on every page load for every user, multiply by your daily active user count. For a 1,000-user Bubble app polling Space on page load, that's 1,000 WU per day just for that one call. Mitigate this by caching Space data in a Bubble data type (updated every 15 minutes via a scheduled workflow) and loading from the Bubble database instead of calling Space directly on each page load. Note: scheduled backend workflows require a paid Bubble plan. RapidDev's team has configured hundreds of Bubble API integrations — if you're building a complex Space dashboard or Python backend integration and want expert guidance, book a free scoping call at rapidevelopers.com/contact.