Skip to content
Cloud infrastructure/devops

linode.com

Linode sandbox and mock API

## Introduction The Linode API provides the ability to programmatically manage the full range of Linode products and services. This reference is designed to assist application developers and system administrators. Each endpoint includes descriptions, request syntax, and examples using standard HTTP requests. Response data is returned in JSON format. This document was generated from our OpenAPI Spe Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
350
Collections
-
Event types
-
example request
curl https://your-linode.slurry.io/v4/account \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 4.145.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 350.

  • GET/account
  • PUT/account
  • POST/account/cancel
  • POST/account/credit-card
  • GET/account/entity-transfers
  • POST/account/entity-transfers
  • GET/account/entity-transfers/{token}
  • DELETE/account/entity-transfers/{token}
  • POST/account/entity-transfers/{token}/accept
  • GET/account/events
  • GET/account/events/{eventId}
  • POST/account/events/{eventId}/read