LayerRail resources can be managed from the console and automated through API-compatible workflows.
Create a personal access token
Open account settings
Sign in to the LayerRail console, open your profile menu, and go to account settings. Create a token
Create a personal access token for the project or automation workflow you want to run.
Store it securely
Save the token in a password manager or CI secret store. Do not commit it to Git.
Authenticate requests
LayerRail API requests use a personal access token in the Authorization header.
export LAYERRAIL_TOKEN="pat-..."
curl https://console.layerrail.com/api/project \
-H "Authorization: Bearer $LAYERRAIL_TOKEN" \
-H "Content-Type: application/json"
Some SDK and CLI flows accept Bearer: with a colon for compatibility, but new integrations should use Authorization: Bearer $LAYERRAIL_TOKEN.
Use scripts carefully
Automation should be project-scoped and repeatable. Store IDs and location names in environment variables instead of hard-coding them into shared scripts.
export LAYERRAIL_PROJECT_ID="pj..."
export LAYERRAIL_LOCATION="us-lax"
Common automation tasks
- List project resources.
- Create virtual machines.
- Rotate access tokens.
- Create inference API keys.
- Query resource state before deployment.
API coverage is still expanding. If an operation is not documented yet, use the console for that action and contact support before automating it.
