# API access for tickets

**URL:** <https://developer.squareup.com/forums/t/api-access-for-tickets/297>\
**Category:** Feature Requests\
**Created:** [May 22, 2020, 8:00pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297 "2020-05-22T20:00:13Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![troymeyer](https://avatars.discourse-cdn.com/v4/letter/t/ecb155/32.png) [@troymeyer](https://developer.squareup.com/forums/u/troymeyer)\
**Post date:** [May 22, 2020, 8:00pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/1 "2020-05-22T20:00:13Z")

</div>

Hello, we have a few customers who are currently using stripe’s point of sale system. They use tickets for in house orders which we cannot access through the API currently. We’d like the ability to create, view, and close tickets.

---

<div class="post-metadata">

**Author:** ![CloosivJames](https://avatars.discourse-cdn.com/v4/letter/c/a3d4f5/32.png) [@CloosivJames](https://developer.squareup.com/forums/u/CloosivJames)\
**Post date:** [May 27, 2020, 6:15pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/2 "2020-05-27T18:15:04Z")

</div>

+1 on this request. We need this as well.

---

<div class="post-metadata">

**Author:** ![Jordan](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@Jordan](https://developer.squareup.com/forums/u/Jordan)\
**Post date:** [May 27, 2020, 6:40pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/3 "2020-05-27T18:40:07Z")

</div>

> [@troymeyer](#):
>
> Hello, we have a few customers who are currently using stripe’s point of sale system.

Do you mean Square? 🙂  
Just want to clarify so I understand the use case! Are you using Stripe for online payment and Square in-person? What kind of businesses is it and can you describe the buyer experience?

---

<div class="post-metadata">

**Author:** ![troymeyer](https://avatars.discourse-cdn.com/v4/letter/t/ecb155/32.png) [@troymeyer](https://developer.squareup.com/forums/u/troymeyer)\
**Post date:** [May 28, 2020, 12:44am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/4 "2020-05-28T00:44:12Z")

</div>

Yes sorry square. We’re using stripe for our payment processor and our business need is that we allow customers to open a tab from their phone, view it as they order, then pay from their phone when they leave or automatically closes by the establishment. We have everything we need except for tickets, we misunderstood that orders are different than tickets which seems the only thing not available in square

---

<div class="post-metadata">

**Author:** ![honeybeecafe](https://avatars.discourse-cdn.com/v4/letter/h/ccd318/32.png) [@honeybeecafe](https://developer.squareup.com/forums/u/honeybeecafe)\
**Post date:** [August 5, 2020, 6:40am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/5 "2020-08-05T06:40:44Z")

</div>

This is a fundamental part of the Restaraunt Processing of Square and needs to be addressed ASAP.

---

<div class="post-metadata">

**Author:** ![DrinkExchange](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/drinkexchange/32/210_2.png) [@DrinkExchange](https://developer.squareup.com/forums/u/DrinkExchange)\
**Post date:** [October 6, 2020, 3:47am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/6 "2020-10-06T03:47:02Z")

</div>

Couldn’t agree more. It’s ridiculous this hasn’t been added yet.

Does anyone have an update as to when this will appear in the API?

---

<div class="post-metadata">

**Author:** ![dfurr](https://avatars.discourse-cdn.com/v4/letter/d/b487fb/32.png) [@dfurr](https://developer.squareup.com/forums/u/dfurr)\
**Post date:** [October 6, 2020, 4:13pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/7 "2020-10-06T16:13:08Z")

</div>

Agree on this. My use-case is for multiple coffee shops/restaurants when they open “tabs” for customers. It would be nice to access the ticketing via the API & ideally a webhook when the ticket is updated.

---

<div class="post-metadata">

**Author:** ![ErikB](https://avatars.discourse-cdn.com/v4/letter/e/e8c25b/32.png) [@ErikB](https://developer.squareup.com/forums/u/ErikB)\
**Post date:** [June 1, 2021, 2:23pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/8 "2021-06-01T14:23:31Z")

</div>

Any update on this?  
I need to access created tickets.

---

<div class="post-metadata">

**Author:** ![David\_096](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@David\_096](https://developer.squareup.com/forums/u/David_096)\
**Post date:** [June 3, 2021, 9:15am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/9 "2021-06-03T09:15:59Z")

</div>

I think not get resolved?

---

<div class="post-metadata">

**Author:** ![reeseb777](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/reeseb777/32/658_2.png) [@reeseb777](https://developer.squareup.com/forums/u/reeseb777)\
**Post date:** [July 6, 2021, 2:56am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/10 "2021-07-06T02:56:57Z")

</div>

+1 on this. Major missing feature for my clients

---

<div class="post-metadata">

**Author:** ![reeseb777](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/reeseb777/32/658_2.png) [@reeseb777](https://developer.squareup.com/forums/u/reeseb777)\
**Post date:** [July 6, 2021, 3:10am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/11 "2021-07-06T03:10:01Z")

</div>

It has been more than one year since this request. Is there any workaround available? This is really a show-stopper and if there is no workaround, I’m probably going to have to advise my client to use a platform other than Square.

---

<div class="post-metadata">

**Author:** ![ram\_paerpay](https://avatars.discourse-cdn.com/v4/letter/r/bbce88/32.png) [@ram\_paerpay](https://developer.squareup.com/forums/u/ram_paerpay)\
**Post date:** [May 19, 2022, 8:41pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/12 "2022-05-19T20:41:12Z")

</div>

Is there any update on this? We would like to see tickets come in real-time for our scenarios. Having APIs to fetch tickets and get webhook events for it will be great

---

<div class="post-metadata">

**Author:** ![chao](https://avatars.discourse-cdn.com/v4/letter/c/839c29/32.png) [@chao](https://developer.squareup.com/forums/u/chao)\
**Post date:** [October 29, 2022, 9:32pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/13 "2022-10-29T21:32:09Z")

</div>

Can we get webhook or API access for open tickets created on Square POS?  
I saw Square KDS or Fresh KDS (3rd party app) can shows the Tickets created on Square POS, so i believe there will be a way to get those events and data.

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [October 31, 2022, 3:57pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/14 "2022-10-31T15:57:37Z")

</div>

Just posted in the other thread but the same holds true. Open tickets on the POS aren’t currently accessible via API or webhooks. 🙂

---

<div class="post-metadata">

**Author:** ![orik](https://avatars.discourse-cdn.com/v4/letter/o/b2d939/32.png) [@orik](https://developer.squareup.com/forums/u/orik)\
**Post date:** [October 7, 2023, 12:00am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/15 "2023-10-07T00:00:33Z")

</div>

Is this ever going to change? Square KDS is not a realistic solution (is anyone anywhere using it?) and building our custom in-house expediting and live inventory apps is the only alternative to switching away from square at this point.

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [October 9, 2023, 3:42pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/16 "2023-10-09T15:42:11Z")

</div>

At this time programmatically accessing open tickets still isn’t available. We hope to have more in the future. 🙂

---

<div class="post-metadata">

**Author:** ![CColotti](https://avatars.discourse-cdn.com/v4/letter/c/cdc98d/32.png) [@CColotti](https://developer.squareup.com/forums/u/CColotti)\
**Post date:** [February 16, 2024, 11:19am UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/17 "2024-02-16T11:19:57Z")

</div>

Well this explains it, I just ran into this trying to build a Gravity form that will just “start” an open ticket. We have a food truck and we want factory workers to pre-order the night before and start their ticket so the next morning we can add the items and send it to the kitchen like a phone order. The farthest we got so far was to just get the “customer” created which is a start, but adding the open ticket with some basic information would save another bit of time. Hard to believe there’s no API for that available after 3 years.

---

<div class="post-metadata">

**Author:** ![policenauts](https://avatars.discourse-cdn.com/v4/letter/p/bc8723/32.png) [@policenauts](https://developer.squareup.com/forums/u/policenauts)\
**Post date:** [March 20, 2024, 4:56pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/18 "2024-03-20T16:56:36Z")

</div>

Just adding that if a Tickets API ever comes into being, it would also be great to be able to POST open tickets as well.

---

<div class="post-metadata">

**Author:** ![osd](https://avatars.discourse-cdn.com/v4/letter/o/ecc23a/32.png) [@osd](https://developer.squareup.com/forums/u/osd)\
**Post date:** [March 21, 2024, 5:13pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/19 "2024-03-21T17:13:58Z")

</div>

I sell tickets myself.  
Here’s how I pull it off.

Use the orders API to create Line items and name each line item as a ticket then if the number of tickets are small enough you can add the ticket names in the note field of the payments API so when the order is paid you can search for the names of the tickets in the dashboard. I think the note parameter allows for over 500 characters so you’ll get enough space for ticket names if there are only a few per order.

---

<div class="post-metadata">

**Author:** ![thirsty](https://avatars.discourse-cdn.com/v4/letter/t/dbc845/32.png) [@thirsty](https://developer.squareup.com/forums/u/thirsty)\
**Post date:** [September 12, 2024, 4:37pm UTC](https://developer.squareup.com/forums/t/api-access-for-tickets/297/20 "2024-09-12T16:37:21Z")

</div>

Any news? It’s a year later and the lack of the ability to see open orders is severely limiting our integration possibilities with Square. Many thanks for your help!

[Next page](https://developer.squareup.com/forums/t/api-access-for-tickets/297.md?page=2)
