--- title: "Get Open Tickets from the Freshworks API Using Python" url: "http://35.223.47.52/blog/get-open-tickets-from-the-freshworks-api-using-python/" date: "2026-08-13T12:58:32+00:00" modified: "2026-08-23T11:20:36+00:00" type: "post" --- # Get Open Tickets from the Freshworks API Using Python [Blog](http://35.223.47.52/blog) / [Tutorials](http://35.223.47.52/blogs/tutorials/) / Get Open Tickets from the Freshworks API Using Python [Tutorials](http://35.223.47.52/blogs/tutorials/) · August 13, 2026 Get Open Tickets from the Freshworks API Using Python ===================================================== ![](https://storage.googleapis.com/knit-website-media/2026/08/64c34ca1e0546a9d333bb35a_Kunal-3-150x150.png)Kunal Mishra 4 min read [](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2F35.223.47.52%2Fblog%2Fget-open-tickets-from-the-freshworks-api-using-python%2F) [](https://twitter.com/intent/tweet?url=http%3A%2F%2F35.223.47.52%2Fblog%2Fget-open-tickets-from-the-freshworks-api-using-python%2F&text=Get%20Open%20Tickets%20from%20the%20Freshworks%20API%20Using%20Python) Table of Contents - [Introduction](#introduction) - [Prerequisites](#prerequisites) - [API Endpoints](#api-endpoints) - [Step-by-Step Process](#step-by-step-process) - [Step 1: Authentication](#step-1-authentication) - [Step 2: Fetch Open Tickets for One Customer](#step-2-fetch-open-tickets-for-one-customer) - [Step 3: Fetch Open Tickets for All Customers](#step-3-fetch-open-tickets-for-all-customers) - [Common Pitfalls](#common-pitfalls) - [Frequently Asked Questions](#frequently-asked-questions) - [Knit for Freshworks API Integration](#knit-for-freshworks-api-integration) Introduction ------------ This article is part of an ongoing series that breaks down the [**Freshworks API**](/blog/full-list-of-knits-crm-api-guides/) in a practical, use-case–driven way. This piece focuses specifically on retrieving **open tickets**, one of the most common operational needs for support analytics, workflow automation, and reporting. Prerequisites ------------- Before making any API calls, ensure the following are in place: - **API Key** Generate your API key from **Profile Settings → API Settings** in your Freshworks account. - **Bundle Alias** This is the unique identifier for your Freshworks account and is required to construct the correct API base URL. You’ll find it in the same API Settings section. API Endpoints ------------- Freshworks exposes simple REST endpoints for querying tickets by status. - **Get open tickets for a single customer** ``` GET /api/tickets?filter=open&customer_id={customer_id} ``` - **Get open tickets across all customers** ``` GET /api/tickets?filter=open ``` Both endpoints return JSON responses and support additional parameters such as pagination and embedded fields if needed. Step-by-Step Process -------------------- ### Step 1: Authentication Freshworks uses token-based authentication. Your API key must be passed in the request headers. ``` headers = { "Authorization": "Token token=your_api_key", "Content-Type": "application/json" } ``` ### Step 2: Fetch Open Tickets for One Customer Replace `{customer_id}` with the actual customer identifier from your Freshworks account. ``` import requests url = "https://yourdomain.myfreshworks.com/api/tickets?filter=open&customer_id={customer_id}" response = requests.get(url, headers=headers) print(response.json()) ``` Use this approach when you’re building customer-specific views or syncing ticket status into account-level workflows. ### Step 3: Fetch Open Tickets for All Customers If you want a global view of unresolved tickets, use the endpoint without a customer filter. ``` import requests url = "https://yourdomain.myfreshworks.com/api/tickets?filter=open" response = requests.get(url, headers=headers) print(response.json()) ``` In production scenarios, this is almost always combined with pagination handling to avoid partial data pulls. Common Pitfalls --------------- This is where most integrations break down. Avoid these mistakes upfront: 1. **Incorrect API key** Expired or copied-with-whitespace keys will fail silently with authentication errors. 2. **Missing or incorrect bundle alias** A wrong subdomain means your request never reaches the right account. 3. **Invalid customer ID** Freshworks does not auto-correct or infer customer identifiers. 4. **Ignoring pagination** Large ticket volumes require explicit handling to avoid truncated datasets. 5. **Hitting rate limits** High-frequency polling without backoff logic will get throttled. 6. **Malformed headers** Authentication headers must follow the exact token format. 7. **Using deprecated API versions** Older endpoints may work today and fail tomorrow, always check versioning. Frequently Asked Questions -------------------------- **How do I find my API key?** Go to **Profile Settings → API Settings** in your Freshworks dashboard. **What exactly is a bundle alias?** It’s the unique identifier for your Freshworks account and forms part of the API base URL. **Can I filter tickets by other statuses?** Yes. The `filter` parameter supports values like `open`, `closed`, and others depending on your Freshworks configuration. **Is there a limit to how many tickets I can fetch?** Yes. Freshworks enforces pagination and rate limits. Always consult the official API documentation for current thresholds. **How should I handle API errors?** Check HTTP status codes, log error responses, and implement retry logic with exponential backoff. **Can I fetch additional ticket details in the same call?** Yes. Use the `include` parameter to embed related resources where supported. **What should I check if authentication fails?** Confirm the API key, ensure it’s active, and verify that it’s passed exactly as required in the headers. Knit for Freshworks API Integration ----------------------------------- If you don’t want to manage authentication quirks, pagination logic, rate limits, and long-term API maintenance yourself, **Knit** provides a cleaner abstraction. Integrate with Knit once, and it handles authentication, authorization, version changes, and operational overhead for the Freshworks API behind the scenes. The result: faster implementation, fewer edge-case failures, and a more resilient integration layer that scales as your usage grows. --- **Ready to build this integration?** Explore Knit’s [Freshworks integration](/integration/freshworks/) or read more about our [Unified CRM API](/integration-categories/unified-crm-api/). ![](https://storage.googleapis.com/knit-website-media/2026/08/64c34ca1e0546a9d333bb35a_Kunal-3-150x150.png)Written by Kunal Mishra Changing integration landscape, one organization at a time‍ Keep Reading ------------ ![](https://storage.googleapis.com/knit-website-media/2026/08/blog-banner-green-640x400.png) [Tutorials](http://35.223.47.52/blogs/tutorials/) ### [How to Create a Slack Bot in 5 Minutes: A to Z Guide](http://35.223.47.52/blog/how-to-create-a-slack-bot/) You can create your own Slack Bot in just a few minutes with the Knit Unified API. Read this step-by-step… August 13, 2026 · 3 min read ![](https://storage.googleapis.com/knit-website-media/2026/08/blog-banner-green-640x400.png) [Tutorials](http://35.223.47.52/blogs/tutorials/) ### [How to Build and Deploy a Microsoft Teams Bot](http://35.223.47.52/blog/how-to-build-and-deploy-a-microsoft-teams-bot/) You can either build Microsoft Teams Bot on your own or you can use Knit's Unified API to create it… August 13, 2026 · 4 min read ![](https://storage.googleapis.com/knit-website-media/2026/08/blog-banner-yellow-scaled-640x400.png) [Tutorials](http://35.223.47.52/blogs/tutorials/) ### [What Should You Look For in A Unified API Platform?](http://35.223.47.52/blog/what-should-you-look-for-in-a-unified-api-platform/) The right unified API can solve all your integration woes at minimal effort and cost. Read this to know how… August 13, 2026 · 14 min read \#1 in Ease of Integrations --------------------------- ![4.9 out of 5 stars](/wp-content/themes/knit/assets/images/g2/g2-star-rating.svg) 4.9 out of 5 stars on G2 ![G2 Leader, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-leader.svg)![G2 Fastest Implementation, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-fastest-implementation.svg)![G2 High Performer, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-high-performer.svg)![G2 Best Est. ROI, Spring 2026](/wp-content/themes/knit/assets/images/g2/g2-best-roi.svg) Put Integrations on Autopilot. Talk to Experts. ----------------------------------------------- Knit is loved by customers across the globe due to our seamless product and white glove support. You'll love us too! [Talk to a Human](/book-demo)