Released on June 11, 2026
Spark CRM v1.1.0 delivers a major expansion of the REST API, giving external systems and integrations full programmatic control over the platform — configuring campaigns, products, payment routing, auto responders, affiliates and subscriptions without ever touching the dashboard.
What’s New
Campaign Configuration
Build and manage entire campaigns through the API:
- Campaigns — create, retrieve and update campaigns
- Offers & Upsells — full CRUD for the products, pricing and subscription configuration behind each campaign
- Affiliates — assign and unassign affiliates to campaigns with payout rules
- Auto Responders — attach and manage per-campaign automated email responders
Products
Create, retrieve and update your product catalog programmatically — ideal for syncing inventory and catalog data from external systems.
Payment Routing
Take full control of payment orchestration via the API:
- Payment Routers — create and update routers with their algorithm and failover settings
- Gateways — attach, update and detach gateways on a router, with priority, weight and processing limits
- Routing Rules — define conditional routing logic with priorities, target gateways and fallback behavior
Decline Salvage Profiles
Configure retry behavior and decline-code handling through the API to maximize recovery on failed payments.
Affiliates
Full lifecycle management of affiliates — profiles, tracking IDs, throttling and status — directly via the REST API.
Subscriptions
Complete programmatic control of recurring billing:
- List & filter subscriptions by status and other factors
- Create administrative subscription records from a customer and billing configuration
- Update the next billing date or billing cycle
- Cancel, pause and restart subscriptions
Bug Fixes
- Fixed array-based validation rules that broke PATCH (partial update) requests on several REST endpoints.
- Hardened REST API validation to prevent database constraint violations (NOT NULL and unique) on create and update.
Breaking Changes
None - this release is fully backward compatible. All new endpoints are additive and existing API behavior is unchanged.
Authentication & Permissions
Every new endpoint is protected by granular API token permissions (for example api:subscriptions.create, api:payment_routers.update). All requests are scoped to the authenticated account, and resources belonging to other accounts return a 404 Not Found.