POST
/
super
/
index
Index a custom content
curl --request POST \
  --url https://api.super.work/v1/super/index \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "rootId": [
    "a2ZSuHnZf"
  ],
  "id": [
    "custom-id"
  ],
  "title": [
    "Note title"
  ],
  "content": [
    "# Content in markdown"
  ],
  "type": [
    "markdown"
  ],
  "updatedAt": [
    "2021-01-01T00:00:00Z"
  ],
  "url": [
    "https://slite.slite.page/p/S1TSuHnZf/Security-at-Slite"
  ]
}'
{
  "title": "Onboarding",
  "url": "https://slite.slite.page/p/S1TSuHnZf/Security-at-Slite",
  "id": "S1TSuHnZf",
  "updatedAt": "2021-01-01T00:00:00.000Z"
}

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Body

application/json
​
rootId
string
required

Root id of the object to gather sources from. This should be created from the UI as a new custom data source.

Example:
["a2ZSuHnZf"]
​
id
string
required

Unique id of the object to index scoped to the rootId

Example:
["custom-id"]
​
title
string
required

Title of the object to index

Example:
["Note title"]
​
content
string
required

Content of the object to index

Example:
["# Content in markdown"]
​
type
enum<string>
required

Type of the object to index. Can be "markdown" or "html"

Available options:
markdown,
html
​
updatedAt
string<date-time>
required

Last update date of the object to index. Used to determine the freshness of the object.

Example:
["2021-01-01T00:00:00Z"]
​
url
string
required

Url of the object to index. Used to redirect to the proper page.

Example:
[
  "https://slite.slite.page/p/S1TSuHnZf/Security-at-Slite"
]

Response

Ok

​
updatedAt
required

Date of the last update of the note

​
url
string
required

Url of the note

​
title
string
required

Title of the note

​
id
string
required

Id of the note

​
explanation
string

For super, gives explanation about the source