B2B API Reference
Patch strategy
Patches the strategy’s mutable display + discovery metadata.
PATCH
Patches the strategy’s display metadata — name, description, visibility.
Doesn’t change the allocation, schedule, or preferences (each has its own
endpoint).
- Auth:
x-api-keyheader (required) - Required scope:
strategies:write
Mutable fields
Only the three metadata fields above are accepted here. Allocation, schedule,
preferences, and fees each use their dedicated route.
maxApy is managed by
Glider and is read-only through the API.
Patch semantics
JSON Merge Patch (RFC 7396):- Omit a field — preserve the current value.
- Send
null— clear (only on nullable fields above). - Send a value — set.
{} is a 200 no-op. Body is strict; unknown keys return 400.
Where to make other changes
- Allocation:
POST /v2/strategies/{strategyId}/versions - Schedule:
PUT /v2/strategies/{strategyId}/schedule - Preferences:
PATCH /v2/strategies/{strategyId}/preferences
Cross-tenant access
Returns404 — strategies you don’t own are not exposed.
Response
Returns the fullStrategy shape (same as GET /v2/strategies/{strategyId}).