Import linked content

How to think about links between your content

To avoid having to import objects in a specific order, use external IDs to reference content that’s not yet imported. This solves problems with circular dependencies and lets you reference non-existent content. Here is how it works:

1. Define external IDs for all content items and assets you want to import in advance.
2. When referencing another content item or asset, use its external ID.
3. Import your content using the upsert methods with an external ID. The system will resolve all references.

This way, you can import your content in any order and run the import process repeatedly to keep your project up to date. In the example below, you will import two content items that reference each other in their Linked items elements.

Example scenario

Say you want to import two related content items: Donate with us and On Roasts articles. Each content item references the other in the Related articles Linked items element. The result will have the following structure:

1. Define external IDs

External IDs are string-based identifiers of items and assets defined by you. You can define new IDs or reuse IDs from the original storage system you are importing content from. It's up to you to ensure no two objects have the same external ID. See more details on using external IDs for imported content. For large projects, consider using GUIDs. To keep things simple here, use 123 and 456 for your two articles.

2. Use external IDs to reference items

When defining the Linked items elements, use external IDs to reference the other content item:

3. Import content

To create a content item, send a PUT request to the /items/external-id/<YOUR_ITEM_EXTERNAL_ID> endpoint. In the body of the request, specify the item's name and content type. See more details on upserting content items. Import content by upserting a language variant. Send a PUT request to the endpoint specifying the language variant you want to insert or update. In the body of the request, specify the values of individual content elements. Notice that you are referencing the Donate with us item even though you haven't imported it yet. Such references are not visible in the UI.

Second content item

Repeat the same process with the Donate with us article. Start by creating the content item: This resolves the reference in the On Roasts item. Lastly, import the content of the Donate with us item by upserting its language variant: Both references are now resolved. To verify, you can view the imported content items in Kontent.ai:

Validate imported content