Set strategy schedule

curl --request PUT \
  --url 'https://api.glider.fi/v2/strategies/01JWZEE2MF30KVRMRX53N88VA4/schedule' \
  --header 'x-api-key: gldr_sk_your_api_key' \
  --header 'content-type: application/json' \
  --data '{ "type": "interval", "frequency": "hourly" }'

const response = await fetch(
  "https://api.glider.fi/v2/strategies/01JWZEE2MF30KVRMRX53N88VA4/schedule",
  {
    method: "PUT",
    headers: {
      "x-api-key": "gldr_sk_your_api_key",
      "content-type": "application/json",
    },
    body: JSON.stringify({ type: "interval", frequency: "hourly" }),
  },
);
const data = await response.json();

{
  "success": true,
  "data": {
    "type": "interval",
    "frequency": "hourly"
  }
}

PUT

strategies

{strategyId}

schedule

curl --request PUT \
  --url 'https://api.glider.fi/v2/strategies/01JWZEE2MF30KVRMRX53N88VA4/schedule' \
  --header 'x-api-key: gldr_sk_your_api_key' \
  --header 'content-type: application/json' \
  --data '{ "type": "interval", "frequency": "hourly" }'

const response = await fetch(
  "https://api.glider.fi/v2/strategies/01JWZEE2MF30KVRMRX53N88VA4/schedule",
  {
    method: "PUT",
    headers: {
      "x-api-key": "gldr_sk_your_api_key",
      "content-type": "application/json",
    },
    body: JSON.stringify({ type: "interval", frequency: "hourly" }),
  },
);
const data = await response.json();

{
  "success": true,
  "data": {
    "type": "interval",
    "frequency": "hourly"
  }
}

Sets the strategy’s rebalance schedule. The new cadence takes effect on the next rebalance cycle for every enrolled portfolio of this strategy, including paused portfolios — they will run on the new cadence the moment they resume.

Auth: x-api-key header (required)
Required scope: strategies:write

Fleet-wide side effect. This call updates the rebalance cadence for every enrolled portfolio of this strategy. Flipping weekly → hourly on a 1,000-portfolio fleet will cause all of those portfolios to rebalance more frequently from the next cycle onward. Do not grant strategies:write to API keys shipped to client-side or end-user-facing applications (mobile apps, browsers, embedded SDKs) — keep that scope on server-side operator/dashboard keys only.

Cross-tenant access

Returns 404 — no existence leak.

curl --request PUT \
  --url 'https://api.glider.fi/v2/strategies/01JWZEE2MF30KVRMRX53N88VA4/schedule' \
  --header 'x-api-key: gldr_sk_your_api_key' \
  --header 'content-type: application/json' \
  --data '{ "type": "interval", "frequency": "hourly" }'

const response = await fetch(
  "https://api.glider.fi/v2/strategies/01JWZEE2MF30KVRMRX53N88VA4/schedule",
  {
    method: "PUT",
    headers: {
      "x-api-key": "gldr_sk_your_api_key",
      "content-type": "application/json",
    },
    body: JSON.stringify({ type: "interval", frequency: "hourly" }),
  },
);
const data = await response.json();

{
  "success": true,
  "data": {
    "type": "interval",
    "frequency": "hourly"
  }
}

B2B API Reference

tRPC Endpoints

Internal Admin Endpoints

Cross-tenant access

​Cross-tenant access

Cross-tenant access