Try our new Setup Skill to automatically integrate Hyperspell into your project
curl --request POST \
--url https://api.hyperspell.com/daemon/redeem-install-token \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'X-As-User: <api-key>' \
--data '
{
"install_token": "<string>"
}
'{
"token": "<string>",
"app_slug": "<string>",
"api_url": "<string>",
"user_key": "<string>",
"email": "<string>"
}Exchange a one-time install token for daemon credentials.
Called by the install script. Token is in the body (not the URL) to avoid exposure in access logs, CDN logs, and browser history.
curl --request POST \
--url https://api.hyperspell.com/daemon/redeem-install-token \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'X-As-User: <api-key>' \
--data '
{
"install_token": "<string>"
}
'{
"token": "<string>",
"app_slug": "<string>",
"api_url": "<string>",
"user_key": "<string>",
"email": "<string>"
}Documentation Index
Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt
Use this file to discover all available pages before exploring further.
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
Optionally set this header to act as a specific user when using an API Key, equivalent to first exchanging the API Key for a User Token
Was this page helpful?