Users

Get user details

get

Update user info

put

Delete user

delete

Query Table Data

https://{your-workspace-slug}.{region}.xata.sh/db/db_branch_name/tables/table_name/query

This endpoint serves data from a given table, inside a specific database's branch.

Expected parameters

NameDescriptionInRequiredSchema
db_branch_name

The DBBranchName matches the pattern `{db_name}:{branch_name}`.

pathstring
table_name

The Table name

pathstring

Query Table

POST
https://{your-workspace-slug}.{region}.xata.sh/db/db_branch_name/tables/table_name/query

The Query Table API can be used to retrieve all records in a table. The API support filtering, sorting, selecting a subset of columns, and pagination.

The overall structure of the request looks like this:

// POST /db/<dbname>:<branch>/tables/<table>/query
{
  "columns": [...],
  "filter": {
    "$all": [...],
    "$any": [...]
    ...
  },
  "sort": {
    "multiple": [...]
    ...
  },
  "page": {
    ...
  }
}

For usage, see also the Xata SDK documentation.

#

Column selection

If the columns array is not specified, all columns are included. For link fields, only the ID column of the linked records is included in the response.

If the columns array is specified, only the selected and internal columns id and xata are included. The * wildcard can be used to select all columns.

For objects and link fields, if the column name of the object is specified, we include all of its sub-keys. If only some sub-keys are specified (via dotted notation, e.g. "settings.plan" ), then only those sub-keys from the object are included.

By the way of example, assuming two tables like this:

{
  "tables": [
    {
      "name": "teams",
      "columns": [
        {
          "name": "name",
          "type": "string"
        },
        {
          "name": "owner",
          "type": "link",
          "link": {
            "table": "users"
          }
        },
        {
          "name": "foundedDate",
          "type": "datetime"
        },
      ]
    },
    {
      "name": "users",
      "columns": [
        {
          "name": "email",
          "type": "email"
        },
        {
          "name": "full_name",
          "type": "string"
        },
        {
          "name": "address",
          "type": "object",
          "columns": [
            {
              "name": "street",
              "type": "string"
            },
            {
              "name": "number",
              "type": "int"
            },
            {
              "name": "zipcode",
              "type": "int"
            }
          ]
        },
        {
          "name": "team",
          "type": "link",
          "link": {
            "table": "teams"
          }
        }
      ]
    }
  ]
}

A query like this:

POST /db/<dbname>:<branch>/tables/<table>/query
{
  "columns": [
    "name",
    "address.*"
  ]
}

returns objects like:

{
  "name": "Kilian",
  "address": {
    "street": "New street",
    "number": 41,
    "zipcode": 10407
  }
}

while a query like this:

POST /db/<dbname>:<branch>/tables/<table>/query
{
  "columns": [
    "name",
    "address.street"
  ]
}

returns objects like:

{
  "id": "id1"
  "xata": {
    "version": 0
  }
  "name": "Kilian",
  "address": {
    "street": "New street"
  }
}

If you want to return all columns from the main table and selected columns from the linked table, you can do it like this:

{
  "columns": ["*", "team.name"]
}

The "*" in the above means all columns, including columns of objects. This returns data like:

{
  "id": "id1"
  "xata": {
    "version": 0
  }
  "name": "Kilian",
  "email": "kilian@gmail.com",
  "address": {
    "street": "New street",
    "number": 41,
    "zipcode": 10407
  },
  "team": {
    "id": "XX",
    "xata": {
      "version": 0
    },
    "name": "first team"
  }
}

If you want all columns of the linked table, you can do:

{
  "columns": ["*", "team.*"]
}

This returns, for example:

{
  "id": "id1"
  "xata": {
    "version": 0
  }
  "name": "Kilian",
  "email": "kilian@gmail.com",
  "address": {
    "street": "New street",
    "number": 41,
    "zipcode": 10407
  },
  "team": {
    "id": "XX",
    "xata": {
      "version": 0
    },
    "name": "first team",
    "code": "A1",
    "foundedDate": "2020-03-04T10:43:54.32Z"
  }
}

There are two types of operators:

  • Operators that work on a single column: $is, $contains, $pattern, $includes, $gt, etc.
  • Control operators that combine multiple conditions: $any, $all, $not , $none, etc.

All operators start with an $ to differentiate them from column names (which are not allowed to start with a dollar sign).

Filter by one column:

{
  "filter": {
    "<column_name>": "value"
  }
}

This is equivalent to using the $is operator:

{
  "filter": {
    "<column_name>": {
      "$is": "value"
    }
  }
}

For example:

{
  "filter": {
    "name": "r2"
  }
}

Or:

{
  "filter": {
    "name": {
      "$is": "r2"
    }
  }
}

For objects, both dots and nested versions work:

{
  "filter": {
    "settings.plan": "free"
  }
}
{
  "filter": {
    "settings": {
      "plan": "free"
    }
  }
}

If you want to OR together multiple values, you can use the $any operator with an array of values:

{
  "filter": {
    "settings.plan": { "$any": ["free", "paid"] }
  }
}

If you specify multiple columns in the same filter, they are logically AND'ed together:

{
  "filter": {
    "settings.dark": true,
    "settings.plan": "free"
  }
}

The above matches if both conditions are met.

To be more explicit about it, you can use $all or $any:

{
  "filter": {
    "$any": {
      "settings.dark": true,
      "settings.plan": "free"
    }
  }
}

The $all and $any operators can also receive an array of objects, which allows for repeating column names:

{
  "filter": {
    "$any": [
      {
        "name": "r1"
      },
      {
        "name": "r2"
      }
    ]
  }
}

You can check for a value being not-null with $exists:

{
  "filter": {
    "$exists": "settings"
  }
}

This can be combined with $all or $any :

{
  "filter": {
    "$all": [
      {
        "$exists": "settings"
      },
      {
        "$exists": "name"
      }
    ]
  }
}

Or you can use the inverse operator $notExists:

{
  "filter": {
    "$notExists": "settings"
  }
}

$contains is the simplest operator for partial matching. Note that $contains operator can cause performance issues at scale, because indices cannot be used.

{
  "filter": {
    "<column_name>": {
      "$contains": "value"
    }
  }
}

Wildcards are supported via the $pattern operator:

{
  "filter": {
    "<column_name>": {
      "$pattern": "v*alu?"
    }
  }
}

The $pattern operator accepts two wildcard characters:

  • * matches zero or more characters
  • ? matches exactly one character

If you want to match a string that contains a wildcard character, you can escape them using a backslash (\). You can escape a backslash by usign another backslash.

You can also use the $endsWith and $startsWith operators:

{
  "filter": {
    "<column_name>": {
      "$endsWith": ".gz"
    },
    "<column_name>": {
      "$startsWith": "tmp-"
    }
  }
}
{
  "filter": {
    "<column_name>": {
      "$ge": 0,
      "$lt": 100
    }
  }
}

Date ranges support the same operators, with the date using the format defined in RFC 3339:

{
  "filter": {
    "<column_name>": {
      "$gt": "2019-10-12T07:20:50.52Z",
      "$lt": "2021-10-12T07:20:50.52Z"
    }
  }
}

The supported operators are $gt, $lt, $ge, $le.

A general $not operator can inverse any operation.

{
  "filter": {
    "$not": {
      "<column_name1>": "value1",
      "<column_name2>": "value1"
    }
  }
}

Note: in the above the two condition are AND together, so this does (NOT ( ... AND ...))

Or more complex:

{
  "filter": {
    "$not": {
      "$any": [
        {
          "<column_name1>": "value1"
        },
        {
          "$all": [
            {
              "<column_name2>": "value2"
            },
            {
              "<column_name3>": "value3"
            }
          ]
        }
      ]
    }
  }
}

The $not: { $any: {}} can be shorted using the $none operator:

{
  "filter": {
    "$none": {
      "<column_name1>": "value1",
      "<column_name2>": "value1"
    }
  }
}

In addition, you can use operators like $isNot or $notExists to simplify expressions:

{
  "filter": {
    "<column_name>": {
      "$isNot": "2019-10-12T07:20:50.52Z"
    }
  }
}

To test that an array contains a value, use $includesAny.

{
  "filter": {
    "<array_name>": {
      "$includesAny": "value"
    }
  }
}

The $includesAny operator accepts a custom predicate that will check if any value in the array column matches the predicate. The $includes operator is a synonym for the $includesAny operator.

For example a complex predicate can include the $all , $contains and $endsWith operators:

{
  "filter": {
    "<array name>": {
      "$includes": {
        "$all": [
          { "$contains": "label" },
          { "$not": { "$endsWith": "-debug" } }
        ]
      }
    }
  }
}

The $includesNone operator succeeds if no array item matches the predicate.

{
  "filter": {
    "settings.labels": {
      "$includesNone": [{ "$contains": "label" }]
    }
  }
}

The above matches if none of the array values contain the string "label".

The $includesAll operator succeeds if all array items match the predicate.

Here is an example of using the $includesAll operator:

{
  "filter": {
    "settings.labels": {
      "$includesAll": [{ "$contains": "label" }]
    }
  }
}

The above matches if all array values contain the string "label".

Sorting by one element:

POST /db/demo:main/tables/table/query
{
  "sort": {
    "index": "asc"
  }
}

or descendently:

POST /db/demo:main/tables/table/query
{
  "sort": {
    "index": "desc"
  }
}

Sorting by multiple fields:

POST /db/demo:main/tables/table/query
{
  "sort": [
    {
      "index": "desc"
    },
    {
      "createdAt": "desc"
    }
  ]
}

It is also possible to sort results randomly:

POST /db/demo:main/tables/table/query
{
  "sort": {
    "*": "random"
  }
}

Note that a random sort does not apply to a specific column, hence the special column name "*".

A random sort can be combined with an ascending or descending sort on a specific column:

POST /db/demo:main/tables/table/query
{
  "sort": [
    {
      "name": "desc"
    },
    {
      "*": "random"
    }
  ]
}

This will sort on the name column, breaking ties randomly.

We offer cursor pagination and offset pagination. The cursor pagination method can be used for sequential scrolling with unrestricted depth. The offset pagination can be used to skip pages and is limited to 1000 records.

Example of cursor pagination:

POST /db/demo:main/tables/table/query
{
  "page": {
    "after":"fMoxCsIwFIDh3WP8c4amDai5hO5SJCRNfaVSeC9b6d1FD"
  }
}

In the above example, the value of the page.after parameter is the cursor returned by the previous query. A sample response is shown below:

{
  "meta": {
    "page": {
      "cursor": "fMoxCsIwFIDh3WP8c4amDai5hO5SJCRNfaVSeC9b6d1FD",
      "more": true
    }
  },
  "records": [...]
}

The page object might contain the follow keys, in addition to size and offset that were introduced before:

  • after: Return the next page 'after' the current cursor
  • before: Return the previous page 'before' the current cursor.
  • start: Resets the given cursor position to the beginning of the query result set. Will return the first N records from the query result, where N is the page.size parameter.
  • end: Resets the give cursor position to the end for the query result set. Returns the last N records from the query result, where N is the page.size parameter.

The request will fail if an invalid cursor value is given to page.before, page.after, page.start , or page.end. No other cursor setting can be used if page.start or page.end is set in a query.

If both page.before and page.after parameters are present we treat the request as a range query. The range query will return all entries after page.after, but before page.before, up to page.size or the maximum page size. This query requires both cursors to use the same filters and sort settings, plus we require page.after < page.before. The range query returns a new cursor. If the range encompass multiple pages the next page in the range can be queried by update page.after to the returned cursor while keeping the page.before cursor from the first range query.

The filter , columns, sort , and page.size configuration will be encoded with the cursor. The pagination request will be invalid if filter or sort is set. The columns returned and page size can be changed anytime by passing the columns or page.size settings to the next query.

In the following example of size + offset pagination we retrieve the third page of up to 100 results:

POST /db/demo:main/tables/table/query
{
  "page": {
    "size": 100,
    "offset": 200
  }
}

The page.size parameter represents the maximum number of records returned by this query. It has a default value of 20 and a maximum value of 200. The page.offset parameter represents the number of matching records to skip. It has a default value of 0 and a maximum value of 800.

Cursor pagination also works in combination with offset pagination. For example, starting from a specific cursor position, using a page size of 200 and an offset of 800, you can skip up to 5 pages of 200 records forwards or backwards from the cursor's position:

POST /db/demo:main/tables/table/query
{
  "page": {
    "size": 200,
    "offset": 800,
    "after": "fMoxCsIwFIDh3WP8c4amDai5hO5SJCRNfaVSeC9b6d1FD"
  }
}

Special cursors:

  • page.after=end: Result points past the last entry. The list of records returned is empty, but page.meta.cursor will include a cursor that can be used to "tail" the table from the end waiting for new data to be inserted.
  • page.before=end: This cursor returns the last page.
  • page.start=$cursor: Start at the beginning of the result set of the $cursor query. This is equivalent to querying the first page without a cursor but applying filter and sort . Yet the page.start cursor can be convenient at times as user code does not need to remember the filter, sort, columns or page size configuration. All these information are read from the cursor.
  • page.end=$cursor: Move to the end of the result set of the $cursor query. This is equivalent to querying the last page with page.before=end, filter, and sort . Yet the page.end cursor can be more convenient at times as user code does not need to remember the filter, sort, columns or page size configuration. All these information are read from the cursor.

When using special cursors like page.after="end" or page.before="end", we still allow filter and sort to be set.

Example of getting the last page:

POST /db/demo:main/tables/table/query
{
  "page": {
    "size": 10,
    "before": "end"
  }
}

Request Body Type Definition

Responses