Skip to main content
Jun 16, 2025 8:14 AM UTC
Solved

Identifying collection id used in Data API using Lucid REST API

Hi 

  1. I am fetching the lucid contents information using REST API https://api.lucid.co/documents/e8fa915b-210e-493e-876e-b851c4a3b42e/contents
    1. Response gives data collections array with collection “id” as string.
  2. I am trying to fetch the collection data items using Lucid Data REST API.
    1. Here the request requires collection id as number.

Can someone help, how I can identify the collection id (number) used in DATA API, using the collectionId get from documentContents RESTAPI.

 

Thanks.

Michael B
Michael BAnswer
Lucid product team
Jun 18, 2025 5:12 PM UTC

I looked to see if there was a reasonably small path to add both IDs to the `/content` endpoint, but unfortunately there is not. There are good reasons we moved away from the ID field, which doesn’t scale to the complexity of data that we have today. With a relatively simple example, it is 1:1 but more complex documents can’t deterministically make that connection.

Comments

Michael B
Lucid product team
Jun 16, 2025 9:03 PM UTC

Hello Psuresh, I am reviewing your question now and will have a response soon.

Translate
Michael B
Lucid product team
Jun 17, 2025 2:07 PM UTC

Unfortunately, I can’t find a deterministic way to connect them either. Our Data APis are considered “legacy” products that are not being actively updated as changes are made. The “id” they take is actually an auto-incrementing ID which effectively just points at the actual id of the collection. The content endpoint provides that actual value.

 

Remaking the Data endpoints to fit our modern APIs is a feature that has been requested before, and I put in a new request to consider it for prioritization. However, it is not currently on our roadmap.

Translate
psureshAuthor
Jun 18, 2025 3:20 PM UTC

Unfortunately, I can’t find a deterministic way to connect them either. Our Data APis are considered “legacy” products that are not being actively updated as changes are made. The “id” they take is actually an auto-incrementing ID which effectively just points at the actual id of the collection. The content endpoint provides that actual value.

 

Remaking the Data endpoints to fit our modern APIs is a feature that has been requested before, and I put in a new request to consider it for prioritization. However, it is not currently on our roadmap.

Hi Michael, thanks for your response… it would have been great if we can get a work around/ patch release from product team to solve this mapping between Lucid Chart API and Data API. 

Translate
Michael B
Michael BAnswer
Lucid product team
Jun 18, 2025 5:12 PM UTC

I looked to see if there was a reasonably small path to add both IDs to the `/content` endpoint, but unfortunately there is not. There are good reasons we moved away from the ID field, which doesn’t scale to the complexity of data that we have today. With a relatively simple example, it is 1:1 but more complex documents can’t deterministically make that connection.

Translate