Requesting Developer Hub access
Asking for Developer Hub access
The Developer Hub does not appear in Settings until an ExpiWell administrator enables it for your account. That is deliberate. API access is granted rather than self-served, so somebody has decided your account should have it and recorded that decision.
Email help@expiwell.com and say what you intend to pull and roughly how often. That is genuinely all we need. The answer shapes the limits below, and a one-line description saves a round trip.
What the administrator sets for you
Access is not a single on/off switch. Four things are configured on your account, and together they cap what any credential you create can do. You do not set these yourself; ask for what you need and they are applied for you.
Which data permissions you may choose from. Studies, participants, responses and media are granted individually. Whatever is not granted appears greyed out when you create a credential. Ask only for what you actually intend to pull, because a permission you never use is a permission that can leak.
How many credentials you may hold at once. Enough to give each pipeline its own, so one can be revoked without stopping the others. Five is typical.
The longest expiry you may set. Every credential expires and has to be replaced. This is the backstop against one outliving the person who created it, and it is the setting most worth discussing if it does not fit how your pipeline runs.
Whether the Developer Hub is available at all. The master switch for your account.
If your needs change later, the same address adjusts them. There is no form to fill in.
Telling whether it is active
Open Settings → Developer Hub. If the section is listed in the left-hand menu and shows a New credential button, it is on.
If the section is missing entirely, the grant has not been applied to your account yet. If it is visible but the button is disabled, you are already at your credential limit; revoke one you no longer use and the button comes back.
For team members
If you are a team member on somebody else's account rather than the account owner, two things follow.
Your credentials read the account owner's studies, not your own, because the Developer Hub acts on behalf of the researcher whose team you are on. The role you hold decides whether you may create one at all: view-only roles can open the page but cannot create a credential, because bulk-exporting data you can otherwise only page through in the dashboard is a different capability.
Your role is re-checked on every single request, not stored on the credential. If your role changes, credentials you already created stop working. There is no window where an old permission level keeps a credential alive.
Next
Once it is on, create a credential and then make your first request.