The Live Table from JSON macro allows you to output a table from a JSON data source.

The macro supports outputting data from a URL or an attached file. 

Using the Table from JSON macro

1. Insert the macro on a page:

  • Start entering /Live Table from JSON  and select the macro
  • Or, in the editor pane, click Insert elements -> View more, find the macro, and insert it on the page

2. Specify the CSV source option:

You can use {pageId} variable in the URL, which means ID of the current page.

You can use the {currentUser.id} variable in the URL, which stands for the email address of the current user.

The case may be to pass this email to the server that generates a JSON file, so that only the specific data related to the current user will be produced.

3. Find the attachment by typing the file name

4. Or configure a URL:

  • Add a URL to JSON
  • Select the Authentication type 
  • Optionally set the login and password settings, the authentication header, and additional headers.

To ensure users re-enter credentials when a macro is copied to another page, ask your Confluence administrator to enable the Live Table from CSV & JSON: Prevent macro copy with credentials option in the Administration console.

The request headers format: 

Header name: header value
 Another header: another value

A colon should separate the header name and its value, headers by line breaks.

5. Enter a JSONPath into the Path to array in the object box or leave it empty if JSON is an array.

Open nested objects with the help of the Expand all nested Objects option

You may visit the "Real-life JSON file: a simple use case to try" page, download our example, and play with the settings live.

You can enter several JSON paths, separated by commas

6. Select an appropriate encoding and data format (Plain text/Wiki markup/Markdown) from the list or add it manually.

7. Save the macro and update the page.

Combine the Live Table from JSON macro with Table Filter, Charts & Spreadsheets macros via the Table Toolbox macro to process table data.

Storing authentication data

Login and password, or a custom authentication header, are encrypted with the AES-256 algorithm using a secret key and saved in the macro parameters.

The secret key is generated uniquely for each installation. It is stored in the encrypted Forge storage and rotated yearly. 

The encrypted authentication data can be used only in your Confluence instance and only for the URL you specified when configuring the macro, so it is impossible to steal and reuse it elsewhere.


Custom Authentication with a Jira/Bitbucket/GitLab access token

1. Create a personal access token in your Jira, Bitbucket, or GitLab account
2. Insert the Table from JSON macro on the Confluence page
3. Add a URL to JSON.
To specify a correct URL for GitLab, visit its API documentation
4. Select the Authentication type: Custom
5. Use Bearer Auth without the username
Change request header: Bearer Y our_Token
 6. Save Request header

In general, a custom header consists of Auth_Type Your_Secret