This page describes how to use REST APIs for Table Grid Next Generation for Jira Cloud. Our APIs endpoints are deployed outside of your Atlassian Site cause we are storing grid data using MongoDB, the root URL of all our endpoints is https://databuckets.net.
You can use this Postman collection to experiment with Table Grid Cloud API. To use it, import it in Postman, then set the appropriate values to collection variables (click on three dots → Edit → Variables). You can enter all values but accountId, then run "Get account id" script which automatically fills accountId variable for you.
Basic authentication scheme is used for authentication.
You can also use Table Grid Cloud postman collection for that.
Basic auth password is a token generated on "API Tokens" page.
You need to provide these credentials for every request in the "Authorization" header. You will get 401 response code if your credentials are incorrect.
Values in columns are stored in the following format:
Checkboxes are stored as booleans.
Integers, Numbers, Dates, DateTimes and Times are stored as numbers. Values of Date, DateTime and Time columns are stored in Unix time format in milliseconds.
Strings, Textareas, Single Select Lists and Sequences are stored as strings. Value of a single select list is a string containing a selected item's title.
Multi Select Lists are stored as lists of strings containing titles of selected items.
Formulas are stored as numbers or strings depending on return type.
Userlists are stored as Maps with the following entries:
"accountId" contains user's account id, which uniquely identifies a user. "accountId" may be missing from the result of "Read Grid Data" method call if a user could not be found. When using "Add Grid Data" or "Update Grid Data" methods, "accountId" MUST be provided, and the rest of the entries are optional.
"value" contains user's full name.
"avatar" contains a link to user's avatar.
The term empty value refers to nulls, empty strings and empty lists.