Important Updates for Zapier Users

Action Required for Current RunSignup Zapier Users by Jan 1, 2027

In conjunction with the addition of an API Registration requirement for all users of the RunSignup API, the RunSignup and TicketSignup Zapier App is being updated to accommodate this new requirement. In addition to your existing API Key and API Secret, all Zapier connections will now require an API Caller Registration Token and API Caller Password.

Follow the steps below to make the transition to the new authentication.

Step 1: Register as an API Caller

Before updating your connection in Zapier, you must generate your API Caller credentials.

1. Log in to your account and navigate to the API Caller Registration page.
2. Review the API Developer Contract and click the box to acknowledge and agree with the terms. 
3. Click the Agree to Contract button. 
4. Provide a brief description of your intended usage (e.g., Zapier integration with CRM (e.g., Salesforce, Hubspot, etc.)) and click Create API Caller.
5. The page will display your API Caller token and password. Copy and securely store the generated credentials. Important: Your API Caller password will only be displayed once upon creation. Make sure to save it in a secure location before leaving the page.
   

Step 2: Add a New Connection in Zapier

Once you have your API Key, API Secret, API Caller Registration Token, and API Caller Password, create the updated connection inside Zapier:

1. Log in to your Zapier account.
2. Click App Connections on the left menu. 
3. Click the blue Create Connection button in the top right corner. 
4. Search for and select RunSignup or TicketSignup. If you see multiple listings, choose the listing without a numbered version (i.e., select ‘RunSignup’ not ‘RunSignup (1.4.0)’).
5. In the authentication pop-up window, enter all four required credentials:
   • API Key
   • API Secret
   • API Caller Token
   • API Caller Password
6. Click Connect to finalize the connection.

Step 3: Update Existing Zaps to Use the New Connection

Because Zapier treats authentication changes of this type as a new connection, existing Zaps must be updated manually.

1. Click Automations (or Folders) on the left menu in Zapier and open a Zap that uses RSU / TSU.
2. Click on the trigger or action step that interacts with RSU / TSU.
3. Navigate to the Setup tab of the step.
4. In the App section, click Change. Then search for and select RSU / TSU.
5. In the Account section, click Change and select the newly created connection from Step 2 above.
6. Navigate to the Test tab of the step and click Test to ensure the authentication works without error. 
7. Review any downstream mapping in your Zap to confirm no unintended impacts from the change. 
8. Click Publish to save your updated Zap.

Repeat these steps for all active Zaps connected to RSU or TSU.

FAQs

• Can my existing Zaps be migrated automatically?
  • No. Adding required authentication fields is a breaking change in Zapier, which prevents automated background migration. Manual re-authentication is required.
• Who on our team can generate these API Caller credentials?
  • Only users logged into the primary RSU / TSU account (or sub-accounts with administrative permissions to manage race/event API settings) can generate API Caller tokens.
• Do I need to generate a new API Caller Token for every Zap?
  • No. You only need to create one API Caller Token and one new Zapier connection. Once created, you can select that same connection across all your Zaps in Zapier.
• Do my original API Keys still work?
  • Yes. Your existing API Key and Secret remain valid and are still required. The API Caller Registration token and secret are added in addition to your API credentials, not as a replacement.
• How can I test if my updated Zap is working correctly without triggering real data?
  • Use the Test Step button inside the Zap Editor for both the trigger and action steps. Zapier will send a test payload using the new connection to verify successful authentication without affecting live production workflows.
• Should I delete my old Zapier connection after migrating?
  • Yes. Once all your active Zaps are reconnected to the new authentication model and verified through testing, delete the old connection in Zapier (Apps > select old connection > Delete) to avoid accidental use in future Zaps.
• What happens if I revoke or delete an API Caller Token in RunSignUp?
  • If an API Caller Token is revoked or deleted from your profile, any Zapier connection linked to that token will immediately fail to authenticate, causing connected Zaps to stop running.
• Does this authentication change affect non-Zapier API integrations?
  • This specific guide is for Zapier users. However, if your organization uses custom API scripts, webhooks, or third-party tools outside Zapier, verify if those integrations also require updating to comply with the new API Caller Registration model.
• What happens if I do not update by January 1, 2027?
  • On January 1, 2027, legacy API calls without a registered API Caller token will be rejected, causing un-updated Zaps to pause or fail. We strongly recommend completing this transition early to avoid automation downtime.