Skip to main content
Lucidite
December 7, 2023

New JSON Standard Import API

  • December 7, 2023
  • 26 replies
  • 4857 views

Hi Lucid Developers!

🌟 We just launched our JSON Import functionality within the Standard Import API, and it's set to revolutionize the way you create and visualize data in diagrams.

🔍 Why is JSON Import a Big Deal?

  • Simplicity and Power: Compared to other import methods, JSON import is less complicated yet more powerful, making it possible to auto-create detailed diagrams.
  • Fully Automated Workflow: You can now automate your entire diagram creation process more quickly. No need to open Lucid - just set up your JSON, send a request to our Import Document endpoint, and let Lucidchart handle the rest.
  • Ideal for Various Use Cases: Whether you're visualizing complex networks or leveraging AI for diagram creation, JSON import has opened up many new possibilities.

👥 Who Should Be Excited?

  • Network Professionals: Visualize intricate networks and data centers with ease.
  • AI Enthusiasts: Bring AI-generated diagrams to life quickly.
  • Automation Gurus: JSON import is the perfect option for automating workflows.

We're eager to see the innovative ways you'll use JSON import. Share examples of how you implement this new functionality or ask questions in the thread below this post

Looking forward to your creations,

Scott P, Lucid API Team 🚀

P.S. Don't forget to check out the Guides section of Lucid’s Developer Documentation for detailed guidance and tips on getting started on Lucid’s Developer Platform!

 

Pinned Reply By Jake C

For an example of how to use this new import, check out this Python project I built that imports completed Jira stories for a specified user. Before we had the Standard Import, we had to try to find this information through Jira and manually pull all the Jira tickets into a Lucid document for a user.

However, now that we have the Standard Import, this script can do all of that automatically. All you have to do is input the email of the Jira user, the year you want stories for, and which Lucid product you want to import them into. Then, the Python script will organize the stories by quarter and create a Lucid document for you.

This script has been super helpful for us going into year-end performance reviews so that we can see what work has been completed for each engineer on our team!

Comments

August 21, 2025

I cam across this Community posting for JSON import via API.  I’m currently trying to import a Lucidchart document saved in JSON, but following the instruction, I get the error:

{
"code": "badRequest",
"message": "Bad or malformed request",
"requestId": "6e921dd7e6e91f10",
"details": {
"error": "Expected JSON body"
}
}

I obtained the .lucid file from the Git repository to test this import feature: https://github.com/lucidsoftware/sample-lucid-rest-applications/tree/main/standard-import

With below API, how can I fix the error?

 

Lucid product team
August 21, 2025

Hi ​@Henry Rockwell,

I can’t see anything immediately wrong with the request you sent. Based on the error, it looks like the document.json file was found, but it had trouble reading the contents. Could you check that your document.json file contains valid json?

Are you willing to share which example from Lucid’s git repository you used? It’s possible that our example is not valid.

August 21, 2025

Hi ​@Henry Rockwell,

I can’t see anything immediately wrong with the request you sent. Based on the error, it looks like the document.json file was found, but it had trouble reading the contents. Could you check that your document.json file contains valid json?

Are you willing to share which example from Lucid’s git repository you used? It’s possible that our example is not valid.

Thank you, ​@Trevor J, for your message.  I zipped up the files in the repo https://github.com/lucidsoftware/sample-lucid-rest-applications/tree/main/standard-import/demo-files/demo/unzipped-contents, then renamed as .lucid and used Postman, but Postman is giving me the errors.

However, if I try the same .lucid file in command line with curl, I was able to import the demo package from the git repository.  So, the first hurdle is cleared.

With this package, now I have replaced the .json file with the document I need to import.  After the curl command returned successful value:

{"documentId":"d4d9ddab-1dab-4311-a787-e753e1d80665","title":"Lucid ローカリゼーション","editUrl":"https://lucid.app/lucidchart/d4d9ddab-1dab-4311-a787-e753e1d80665/edit","viewUrl":"https://lucid.app/lucidchart/d4d9ddab-1dab-4311-a787-e753e1d80665/view","version":150,"pageCount":68,"canEdit":true,"creatorId":170886776,"lastModified":"2025-08-21T17:52:28Z","lastModifiedUserId":170886776,"trashed":null,"status":null,"classification":null,"customAttributes":[],"customTags":[],"parent":null,"product":"lucidchart","created":"2025-08-21T17:52:28Z"}

I went to the URL, but everything is empty.  No chart is imported.  I see the correct number of tabs (or pages) that my document has, and the tab text is also correct based on my JSON file, but all pages are blank.  What could be causing this?

 

Lucid product team
August 21, 2025

@Henry Rockwell,

That’s great that the correct pages are showing up. It’s difficult to tell why the shapes aren’t appearing correctly without seeing the JSON itself. I’ve sent you an email to continue debugging privately.

October 15, 2025

Hi there,

I could import JSON into Lucid.
But I wondered whether I can then manually polish the chart, and send it back via Standard import API for further programmatic use.

I could receive it, although without the JSON itself with this call:
curl -X GET "https://api.lucid.co/documents/b3d6b712-a10c-4c69-856e-c92b6c0977b2/export?format=standard_import" -H "Authorization: Bearer $LUCID_API_TOKEN" -H "Lucid-Api-Version: 1" -o exported_model.lucid

Is there a way to GET also the JSON with the content of the page (shapes etc)?

Sorry if the answer is elsewhere, but I could not find it..


BTW, if this is of any help, this is my output:
 

 

Lucid product team
October 15, 2025

Hey Jan.Zalesak.  Our standard import flows do not support any methods for exporting  document content.  We do have a “Document Contents” API endpoint that will return you the contents of a document, but it does not include positioning data for shapes.  Additionally, standard import does not support modifying existing documents, only creating new documents, so If you make programmatic adjustments to a given documents contents, and then wish to re-import those into Lucid, it would need to be done into a new document.