How do custom integrations work, and what credentials and permissions do they get?

Use a Custom App to give a system you build access to the Endless API. A company Admin or Owner creates it and chooses a team role suited to its work: Editor, Operator, Guest, Sales Rep, Fulfillment Service, or Customer Service. Admin and Owner are not available for Custom Apps.

The selected role determines what the app can read or change. Choose Guest for read-only work, or an appropriate operational role for writes. Changing the role affects subsequent requests. Your plan must include API access.

Existing Custom Sales, Custom Fulfillment, Custom Product, Read Only Data, and Operations integrations can be converted to Custom Apps. Conversion preserves their integration record, API key, building connections, and order history, but replaces their old permissions with the selected role. Review what the connected system needs before converting. Celigo keeps its separate connector setup.

An unconverted custom integration keeps the fixed role associated with its original type. A permission error can mean its role does not allow the requested action; ask your Admin or Owner to review the app’s role. Contact Endless support if no role is assigned.

Admins and Owners manage credentials on the Custom App page. Use the provided credentials in your connected system, and contact Endless support to rotate them. Deleting the integration stops its credentials from working.

Custom Apps can act as inventory sources and fulfillment providers. Your system uses the API to supply updates; selecting an app as the provider does not make Endless push a warehouse order to it automatically.

See custom app setup and API connection headers.