Self-Service Inventory & Labor API Tokens

Warning: Crunchtime has transitioned to a secure, self-service API token management model. The legacy tokesn are deprecated as of the cutover date of November 2, 2026. To avoid any disruption to your integrations, please plan to replace your legacy tokens by September 1, 2026—before the final cutover date of November 2, 2026. System administrators should immediately migrate to generating self-service tokens directly within Enterprise Manager.

How to Generate Your Self-Service Tokens 

Administrators can enable and provision tokens in just a few steps:

Step 1: Grant Administrator Permissions

1. In Enterprise Manager, navigate to Security > User Groups.

2. Select and edit the desired User Group that contains the user who will be leveraging the API.

3. Enable the Application Users > API Tokens control.

Step 2: Generate the Token for an Application User

1. Go to Security > Application Users.

2. Edit the specific record for the account requiring API access (we highly recommend using a dedicated account, e.g.,"API User", rather than a personal staff account).

3. Select the API Tokens tab to instantly generate and manage your environment tokens.

For a guided walk-through, please take our interactive Manage Your API Tokens Feature Tour or check out the Crunchtime Developer Hub for more information.

These API tokens are used as a basic authorization attribute for requests at the edge of our infrastructure, where rate limiting and DDoS protection are applied. All API requests require valid, authorized Crunchtime User credentials for the application, specifically the User ID and Password for the processing user account used by the API request. 
 

What is changing?

Crunchtime has transitioned to a secure, self-service API token management model. Beginning November 2, 2026, these legacy tokens will no longer work. Customers using legacy tokens must create new tokens through Crunchtime’s new self-service API Token process and update their integrations before the deadline. 

Why is Crunchtime making this change?

The new API Token process supports industry-standard encryption and role-based access. This new process also includes audit logs which provide insight into who created or modified tokens and when.
 

How do I know if my organization is affected?

Your organization is affected if you have integrations that use API tokens created prior to April 2026, using Crunchtime’s legacy manual token request process.
 

What do I need to do?

If your organization uses legacy API tokens:

1. Create new tokens using the self-service API Token process.

2. Update integrations to use the new tokens as needed.

3. Test the integration to confirm data is flowing as expected.

4. Make sure all legacy tokens have been replaced before November 2, 2026.
    

What happens if I don't replace my legacy token?

Legacy tokens will stop working on November 2, 2026. Any integration that still relies on a legacy token may stop functioning, which could interrupt data flow and potentially impact business operations.

We recommend making the change as soon as possible rather than waiting until the deadline.
 

Will my existing legacy tokens continue working until November 2?

Yes. Legacy tokens are scheduled to stop working on November 2, 2026. However, we recommend transitioning before the deadline so your team has time to update and test integrations.
 

Do I need to replace every API token?

Yes, you should replace all legacy API tokens that are still being used by a user or by an integration. Check with your organization's integration or technical team to identify which tokens are currently active. If you are not sure what tokens are currently being used, please contact Support for further assistance. 
 

What if multiple people or teams use API tokens?

We recommend sharing this information with anyone in your organization who manages integrations or uses API tokens. Each team should identify any integrations using legacy tokens and make sure they are updated before the deadline.
 

When was I notified about this change?

Crunchtime began notifying customers via email about the legacy API token transition in April 2026. Emails were sent to customer contacts associated with affected accounts to provide time to identify legacy tokens, complete the transition, and address any questions before the November 2, 2026 deadline.
 

What if I need additional help?

If you have questions about replacing your legacy API tokens or updating an integration, contact Customer Success or submit a Support ticket for assistance.

Legacy API Tokens can be accessed here until November 2, 2026.