Skip to main content
Solved

Rest API inconsistency with documentation 2 ask

  • April 2, 2026
  • 8 replies
  • 39 views

Michel L
Forum|alt.badge.img+13

Hi,

One year ago I tell that:

According to the documentation, “https://api.lucid.co/documents/search” endpoint gives the result:

"documentId": "110808fd-4553-4316-bccf-4f25ff59a532",
  "title": "document title",
  "editUrl": "https://lucid.app/lucidchart/110808fd-4553-4316-bccf-4f25ff59a532/edit",
  "viewUrl": "https://lucid.app/lucidchart/110808fd-4553-4316-bccf-4f25ff59a532/view",
  "version": 101,
  "pageCount": 5,
  "canEdit": false,
  "created": "2019-04-22T13:47:23Z",
  "creatorId": 12345,
  "lastModified": "2020-06-26T16:29:37Z",
  "lastModifiedUserId": 54321,
  "customAttributes": [],
  "customTags": [
    "in progress"
  ],
  "product": "lucidchart",
  "status": "Complete",
  "classification": "Private",
  "trashed": null,
  "parent": null,
  "owner": {
    "id": 123456,
    "type": "user",
    "name": "John Doe"
  }

especially tells that there is a response field “owner” which is good.

But unfortunately in the real world the result is :

documentId: 'efde95db-0d4e-4173-a6a4-c49fac4cc046',
    title: 'Sample Diagram 19',
    editUrl: 'https://lucid.app/lucidchart/efde95db-0d4e-4173-a6a4-c49fac4cc046/edit',   
    viewUrl: 'https://lucid.app/lucidchart/efde95db-0d4e-4173-a6a4-c49fac4cc046/view',   
    version: 385,
    pageCount: 3,
    canEdit: true,
    creatorId: 128780733,
    lastModified: '2024-02-16T18:17:39Z',
    lastModifiedUserId: 128780733,
    trashed: null,
    status: 'Draft',
    classification: null,
    customAttributes: [],
    customTags: [],
    parent: null,
    product: 'lucidchart',
    created: '2024-02-16T09:46:39Z'

 

The reply was

The document owner information is not returned if the requesting token only has access to the document because its publicly published.

I see that this is not stated in the documentation. I will get it updated.

I asked for an explanation

      Hi ​@Michael B,

      What does that means?

      I’m using:

             "authorizationUrl": "https://lucid.app/oauth2/authorize",
             "tokenUrl": "https://api.lucid.co/oauth2/token",
             "scopes": ["lucidchart.document.content:readonly"],

One year after for now I get no reply

 

Bests regards.

Best answer by Michael B

I’ve submitted a feature request, but have no ETA. Unfortunately, you are correct. In the meantime, two calls will be necessary to get the owner.

Comments

Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • April 2, 2026

Weird. I must have lost track of it; Sorry about that.

 

The definition for owner actually lives in the GET Document endpoint (and should be linked to by other endpoints that share that response resource.)

 

`Published` documents do not require any authorization with Lucid at all. They are available to the world without logging in. A common use case would be a diagram explaining an open source institution.

https://help.lucid.co/hc/en-us/articles/16181914460692-Publish-or-embed-a-Lucid-document

 

If you see cases where that does not apply and the owner is not returned, submit a ticket and we will explore further. I am not aware of other exceptions.


Michel L
Forum|alt.badge.img+13
  • Author
  • April 2, 2026

No problem.

Yes I use Get Document for now but it makes two calls instead of one.

So if your response to documents/search contains a bunch of document (which is often the case), you must iterate and makes a call for each returned document one which is time consuming.

Regards. 


Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • April 2, 2026

I may be misunderstanding you.  Search documents should also return owner information. The documentation about owner was only added to GET documents.


Michel L
Forum|alt.badge.img+13
  • Author
  • April 3, 2026

I mean. If sometimes “https://api.lucid.co/documents/search” returns the owner, I don’t know why it does not return that always.

Regards


Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • April 7, 2026

Hmm, perhaps I have my facts wrong. Researching now and will be in touch.


Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • April 7, 2026

I apologize for the confusion; I had some facts incorrect. I have created an internal story to get documentation correct regarding this. Additionally, that story includes investigating the differences and fixing any that don’t have a justification.

 

  • GET /documents/:id returns owner
  • GET /accounts/me/documents/search returns owner
    • It also returns other undocumented fields that might be useful to some. Given this is a Enterprise-Shield endpoint, those additional fields are related to that product.
  • GET /documents/search does not return owner

I am unaware of a reason why /document/search does not include owner given that the base GET does. I do not have a timeframe for when that will be fixed, but you are correct that something is wrong.

 

Can you double check `If sometimes “https://api.lucid.co/documents/search” returns the owner,`? I shouldn’t ever return it currently, but I have been wrong before. ;)


Michel L
Forum|alt.badge.img+13
  • Author
  • April 7, 2026

I confirm that “https://api.lucid.co/documents/search” never returns the owner.
But yes if it could as i say it will be great!

About GET /accounts/me/documents/search, i could never use that cause it need Enterprise-shield which as I said in other post is a pity because I think We could expect that as soon as we have enterprise subscription (without enterprise shield).


Michael B
Forum|alt.badge.img+4
  • Lucid product team
  • Answer
  • April 9, 2026

I’ve submitted a feature request, but have no ETA. Unfortunately, you are correct. In the meantime, two calls will be necessary to get the owner.