AMS Integration: Applied Epic
The Applied Epic integration connects Broker Buddha AI to your Applied Epic system through Applied's APIs so BB AI can fetch client, contact, location, and policy data on demand — and write signed BOR Letters and other documents back into Applied Epic.
Unlike the AMS360 integrations, Applied Epic uses on-demand data access rather than nightly bulk imports. This article walks through what that means in practice, how to obtain your API credentials in the Applied DevCenter, how to configure the connection in BB AI, and how to troubleshoot common issues.
🔐 Who can configure this integration? Only Account Owners and Billing Managers can set up or change integrations. Standard Users do not have access to the Settings → Integrations area.
⚠️ How Applied Epic's Integration Mode Differs
The Applied Epic configuration page opens with an important warning: Periodic Update Not Available.
Applied Epic only supports on-demand data access. When you need customer data, BB AI will fetch it directly from your Applied Epic system in real time. No data is stored locally unless you specifically request it.
In plain language:
- ❌ No nightly sync. Unlike the Vertafore AMS360 integrations, BB AI does not pull a full copy of your Applied Epic data every 24 hours.
- ✅ Real-time lookup. When you need a record in BB AI, it's fetched from Applied Epic on demand.
- ✅ Writes are supported. You can upload signed BOR Letters and other documents from BB AI into Applied Epic.
💡 If you're comparing AMS integrations: AMS360 mirrors your data into BB AI; Applied Epic queries Applied Epic when you need it.
🖼️ [Image placeholder: screenshot of the Integration Mode card with the "Periodic Update Not Available" warning]
✅ Before You Begin
You'll need API credentials generated in the Applied DevCenter:
- API Key (called Consumer Key in DevCenter)
- API Secret (called Consumer Secret in DevCenter)
You'll also need:
- An Applied DevCenter account (you can register for free)
- A Mock App in DevCenter to obtain your initial credentials
- App Promoter permission in DevCenter to move your app to production (see Promotion: Move to Production below)
💡 The full Applied-side process takes up to 15 minutes for initial registration and credential generation, plus 2–5 business days for Applied Admin to approve the production promotion.
🧭 Opening the Applied Epic Configuration
Step 1: Go to Settings ⚙️ → Integrations. Step 2: Click the Available sub-tab. Step 3: Find the Applied Epic card under Agency Management Systems. Step 4: Click Configure.
🖼️ [Image placeholder: screenshot of the Integrations Available tab with the Applied Epic card highlighted]
You'll land on the Applied Epic configuration page with an Available status badge.
⚙️ Configuring the Integration
The Configuration section is where you enter the credentials you generated in the Applied DevCenter.
Step 1: Enter Your Credentials
- API Key (required) — the API key generated in your Applied Epic system (Consumer Key in DevCenter)
- API Secret (required) — the API secret that pairs with your API key (Consumer Secret in DevCenter)
🖼️ [Image placeholder: screenshot of the API Key and API Secret fields]
Step 2: Confirm Your Environment
- Environment — automatically determined based on your deployment (e.g., Production Environment)
You don't need to set this manually. The page displays a confirmation like:
"Environment is automatically determined based on your deployment. You are connected to Applied Epic production endpoints."
Step 3: Test and Enable
The footer has three buttons:
- Cancel — discards changes and returns to the Integrations list
- Test Connection — verifies your API Key and API Secret without enabling
- Enable Integration — saves the configuration and activates the connection
💡 Always run Test Connection before clicking Enable Integration so you can confirm your credentials are valid before relying on the integration.
🖼️ [Image placeholder: screenshot of the Cancel / Test Connection / Enable Integration buttons]
📋 Setup Instructions: Generating Credentials in the Applied DevCenter
The configuration page includes a Setup Instructions card titled "Applied DevCenter Getting Started Guide". The full process has three stages — Registration, Create an App, and Promotion. Reproduced here for reference:
🪪 Registration — Create an Account
To use Applied APIs, you need a registered account in the DevCenter.
- Click Login → Create new account.
- Complete the registration form.
- Click Create new account at the bottom of the form.
- After you submit the form, you'll receive an email with an activation link.
- Click the link in the email to activate your registration.
🛠️ Create an App — Get Your API Key
To start using an API, you must create a mock app and obtain an API key.
- At the top of the Applied DevCenter landing page, click Mock Apps.
- Click Add Mock App.
- Provide a name for the mock app (we recommend "BB AI").
- Provide a description for the app.
- Select the API products you want to associate with the app. We recommend:
- Accounts
- Attachments Access Levels
- Attachments
- Attachment Folders
- Clients
- CRM Module
- Employees
- Opportunities
- Organizations
- Click Submit.
- On the Mock Apps page, check the status of your apps (all apps are approved by default).
- When your app status is Approved, click the name of the app. You'll find the Consumer Key (API key) and Consumer Secret (API secret) on the opening detail page.
- Copy the API key and API secret and paste them into the Applied Epic integration form in BB AI.
🚀 Promotion — Move to Production
To request to promote your app to production:
- On the Mock Apps page, select the mock app and click Promote to Prod.
- Complete the basic details for the app in the form and send it to Applied Admin for evaluation.
- Requests may take two to five business days to process. Once processed, you'll receive an email notification.
- Visit the Projects page to test the app in production.
- Invite your team members to the project. They must have permission to create apps.
⚠️ Note: You require App Promoter permission to promote an app. Contact your system administrator or use Contact Us in the DevCenter to request App Promoter permission.
🔗 Helpful link: Applied Developer Center (linked from the Setup Instructions card)
🖼️ [Image placeholder: screenshot of the Setup Instructions card showing the three-stage Registration / Create an App / Promotion process]
📥 Integration Capabilities & Data Reference
Below the Configuration section, the page shows a full Integration Capabilities matrix. This tells you exactly which data types BB AI can:
- Import from AMS — pull from Applied Epic into BB AI on demand
- Create in AMS — push new records into Applied Epic
- Update in AMS — modify existing records in Applied Epic
Each row is marked with one of four statuses (per the Legend):
- 🚫 Not available from AMS
- 🟡 Available from AMS but not live
- ✅ Available and Live
- ⚪ n/a — Data not stored in system
You can switch between Card View and Table View depending on what's easier to read.
💡 Periodic imports for Applied Epic = None. This is shown explicitly under Integration Capabilities and reinforces that Applied Epic data is fetched on demand, not on a schedule.
Data types in the matrix include: Insureds, Insured Contacts, Attachments, Markets, Underwriter Contacts, Policy Coverage, Policy Premium, ACORD Non-Scheduled Exposures, ACORD Scheduled Exposures (Locations, Premises, Hazards, Subjects of Insurance, Workers Comp, Commercial Vehicles, Drivers, Buildings), and Audit History.
🖼️ [Image placeholder: screenshot of the Integration Capabilities matrix with the legend and a few rows visible]
✨ Applied Epic Integration Features
At a glance, the Applied Epic integration enables you to:
- ✅ Import clients, contacts, and locations from your Applied Epic system
- ✅ Upload signed BOR Letters or other documents to Applied Epic in any folder
- ✅ Access files in Applied Epic for Market Submissions in BB AI
💡 Best Practices
- Plan ahead for the production promotion. Mock App credentials will get you started, but your BB AI integration runs against production endpoints — and Applied's promotion review can take 2–5 business days. Start the promotion process early.
- Use a clearly named DevCenter app (we recommend "BB AI") so the connection is easy to identify and audit later.
- Select the recommended API products when creating your Mock App. Skipping any of them — especially Attachments and CRM Module — can cause features in BB AI to fail.
- Run Test Connection before enabling. A failed test is far easier to diagnose before live data is moving.
- Confirm App Promoter permission with your DevCenter admin before you reach the promotion step. Without it, the Promote to Prod button won't be available.
- Remember the on-demand model. If a record looks "missing" in BB AI, that's expected — BB AI only fetches Applied Epic data when you ask for it.