# API help

**URL:** <https://forum.astro-colibri.science/t/api-help/456>\
**Category:** Helpdesk + Releases + Feature requests\
**Created:** [October 17, 2025, 5:07pm UTC](https://forum.astro-colibri.science/t/api-help/456 "2025-10-17T17:07:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![FredDJN](https://avatars.discourse-cdn.com/v4/letter/f/13edae/32.png) [@FredDJN](https://forum.astro-colibri.science/u/FredDJN)\
**Post date:** [October 17, 2025, 5:07pm UTC](https://forum.astro-colibri.science/t/api-help/456/1 "2025-10-17T17:07:38Z")

</div>

Hi

I wish I could have any help about the API.

A few weeks ago, I integrated a request to the Astocolibri server from Siril. The goal is to retrieve the coordinates raDec of one selected transient in order to perform a photometric analysis en Siril.

Previously I used such a request:

[https://astro-colibri.science/event?trigger\_id=SN%2025coe](https://astro-colibri.science/event?trigger_id=SN%2025coe)

Unfortunatly, it looks the request structure changed a bit, because I now get an

| |
| --- |
| |

```bash
internal_error "cannot unpack non-iterable NoneType object"

```

| |
| --- |

I could not find out the way to modify the request, even with the help of the API documentation.

Could you help please?

Regards

Fred

---

<div class="post-metadata">

**Author:** ![Fabian.Schussler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.astro-colibri.science/fabian.schussler/32/25_2.png) [@Fabian.Schussler](https://forum.astro-colibri.science/u/Fabian.Schussler)\
**Post date:** [October 17, 2025, 5:59pm UTC](https://forum.astro-colibri.science/t/api-help/456/2 "2025-10-17T17:59:33Z")

</div>

Hi Fred,

thanks for your message!  
The short answer is: The functionality of the /event endpoint indeed changed a bit (at the moment it requires to be called with a trigger\_id and no longer accepts the name of the sources). In order to find the event you are looking you can follow the example in the [interactive notebook](https://colab.research.google.com/drive/1SbGpU9Lh8Z-zuwLyqufQaTD5tHX9tKs2?usp=sharing). For SN 2025coe, the trigger\_id to call is “TNS2025coe” =\> [https://astro-colibri.science/event?trigger\_id=TNS2025coe](https://astro-colibri.science/event?trigger_id=TNS2025coe)

Longer answer: You caught us in the middle of a development that aimed to improve the endpoint(s). The changes have already been implemented and will be part of our next release. This will bring back the functionality to retrieve events directly via their name via the /event endpoint. The enhanced features include faster and more extensive searches: you’ll be able to use different identifiers of each event (including trigger\_ids, source\_names, the internal names used by the disovery instruments, etc.). Stay tuned 😉

---

<div class="post-metadata">

**Author:** ![FredDJN](https://avatars.discourse-cdn.com/v4/letter/f/13edae/32.png) [@FredDJN](https://forum.astro-colibri.science/u/FredDJN)\
**Post date:** [October 17, 2025, 8:11pm UTC](https://forum.astro-colibri.science/t/api-help/456/3 "2025-10-17T20:11:31Z")

</div>

Thanks Fabian for your quick reply.

So for now, and as a workaround, it looks like the prefix TNS should be used for the supernova.

I will modify the code of XPhoto-Siril to comply with this. The goal is to keep on using it among the RAPAS community.

Then, I will try to follow the mods you can introduce. Or maybe there is a logfile I can check in order to be up to date as soon there is a new release?

Thank you for you time and your support.

Fred

---

<div class="post-metadata">

**Author:** ![Fabian.Schussler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.astro-colibri.science/fabian.schussler/32/25_2.png) [@Fabian.Schussler](https://forum.astro-colibri.science/u/Fabian.Schussler)\
**Post date:** [October 17, 2025, 8:29pm UTC](https://forum.astro-colibri.science/t/api-help/456/4 "2025-10-17T20:29:21Z")

</div>

Hi,

yes, the trigger\_id for SNe is easy to guess: use the name of the event and replace the "SN " with “TNS”. Btw. the identifier after “TNS” is the official Transient Name Server identifier, so there is some consistency.

As you know, we are announcing new releases here on the discussion forum. The official changelog is always also available on [Astro-COLIBRI](https://astro-colibri.science/releases)

Cheers,  
Fabian

---

<div class="post-metadata">

**Author:** ![Fabian.Schussler](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.astro-colibri.science/fabian.schussler/32/25_2.png) [@Fabian.Schussler](https://forum.astro-colibri.science/u/Fabian.Schussler)\
**Post date:** [December 2, 2025, 4:32pm UTC](https://forum.astro-colibri.science/t/api-help/456/5 "2025-12-02T16:32:38Z")

</div>

Our latest release (v2.25.0) should fix this issue. Please let us know in case you continue so see errors!

---

<div class="post-metadata">

**Author:** ![FredDJN](https://avatars.discourse-cdn.com/v4/letter/f/13edae/32.png) [@FredDJN](https://forum.astro-colibri.science/u/FredDJN)\
**Post date:** [December 5, 2025, 6:28pm UTC](https://forum.astro-colibri.science/t/api-help/456/6 "2025-12-05T18:28:31Z")

</div>

Thanks Fabian for the feedback.  
I had a quick look at the API and it seems to be OK now (I mean searching an even with the name rather than the Id).  
I just have to implement the modification in XPhoto-Siril.  
It’s great!!!

Tnx

Fred