What’s new at Endless
API changes, deprecations, and important updates for your integrations.
Sales channels now carry an optional handle — a short, stable identifier that travels with the channel even if the display name changes. You can set a handle when creating a channel, and edit it on the channel header card; it auto-suggests a kebab-case version of the channel name and you can override it. Handles are lowercased, validated against the allowed shape, and must be unique inside your company; the same handle can be reused across companies.
Automations, scheduled jobs and connector-side ingest now run as a single system actor rather than borrowing the identity of whatever set them off. Wherever you read who performed something — an activity record, an audit trail — work with no person or integration behind it reports the system, instead of a user you might otherwise try to resolve to a real account.
The system actor is authorized like any other: it holds a role and a scope, so background work passes the same permission checks as a foreground call. Work your own integration performs is still attributed to your integration.
The Endless API documentation at docs.endlesscommerce.com is now organized by category, including areas like orders, inventory, and shipments. A new getting started guide has also been added for teams connecting to the API for the first time.
The updated structure makes it easier for developers and operators to understand how Endless data is organized and where to find the endpoints they need.