AIDE Developer Portal
The AIDE Developer Portal is a separate AdvantaHealth product (repo: AdvantaHealth/AIDE) that handles everything around the AFCore SDK outside of the SDK itself: account access, API keys, member rosters, delivery logs, and support tickets.
This page is a short pointer for AFCore consumers. AIDE has its own portal, its own UI, and its own documentation — go there for step-by-step flows.
What AIDE provides to AFCore consumers
| AIDE surface | What you get | Where it shows up in AFCore |
|---|---|---|
| Access | Org tenant + role | Determines whether you can issue Production keys |
| API Keys | clientId / clientSecret per environment | Passed to AFCoreConfig |
| Members | Eligibility roster + per-member program & entitlements | Drives signInOrCreateMember, profile(), programs() |
| Delivery Logs | Server-side record of every event the SDK posted | Source of truth when SDK behavior is unclear |
| Support | Tickets pre-attached with env, member id, recent events | Faster triage than raw email |
Getting access to AIDE
Ask your AdvantaHealth Account Manager to invite you to your organization's AIDE tenant. Once you're in, the portal's own onboarding will walk you through the rest.
Where AIDE ends and AFCore begins
- AIDE is the control plane — humans configuring the system in a browser.
- AFCore is the client SDK — code running inside the consumer app, talking to the AdvantaHealth API at runtime.
The handoff between them is the clientId / clientSecret you copy from AIDE into AFCoreConfig. Everything else is independent.
Pages here
The following pages summarize what AFCore expects from each AIDE surface — they are not a substitute for the AIDE portal itself.
- API Keys — what
AFCoreConfigneeds - Members — the two enrollment models AFCore supports
- Troubleshooting — using AIDE's delivery log when AFCore misbehaves