API token
White Label owners/developers can create bearer/API tokens for supported REST endpoints instead of sharing a portal password with an external application.
White Label owners/developers can connect supported IEBC records to outside tools without exposing the whole tenant. Create scoped bearer/API tokens for supported endpoints or send signed event payloads to HTTPS webhooks, including Zapier Catch Hook URLs; outgoing requests use an IEBC signature header and retry handling.
White Label owners/developers can create bearer/API tokens for supported REST endpoints instead of sharing a portal password with an external application.
Tokens can be limited to supported resources/operations such as clients, orders, tasks or catalog data so an integration receives only the access it requires.
IEBC can send event payloads to configured HTTPS endpoints and signs outgoing requests with X-IEBC-Signature; retry processing is handled by the application/cron workflow.
A Zapier Catch Hook URL can be used as the outgoing webhook destination so supported IEBC events can trigger a Zap without giving Zapier unrestricted tenant credentials.
Examples include sending a new order to reporting, reacting to status changes, or moving supported task/catalog/client data into an approved external workflow.
The embroidery business owner, manager or authorized staff. Customer-facing actions only appear where the workflow requires customer participation.
Availability depends on the IEBC plan. See the pricing page for current Production Management Suite limits.
These tools are part of IEBC Production Management. Plan limits vary from Forever Free through White Label.
View Production Management