Developer tools
CHAMPREP developer tools provide a consistent way to automate supported workflows without calling individual service backends. Authentication, service access, scopes, usage controls, and audit context are applied at the API Gateway.
Choose an integration path
Section titled “Choose an integration path”| Path | Best for | Start here |
|---|---|---|
| API Gateway | Direct HTTPS integrations and custom applications | API Gateway overview |
| CHAMPREP CLI | Interactive terminal work, scripts, and CI jobs | CLI overview |
| Webhooks | Event-driven integrations that should not poll | Webhooks |
| Official SDKs | Typed clients for supported services and frameworks | CHAMPREP SDKs |
| SCIM 2.0 | Enterprise identity-provider provisioning | SCIM provisioning |
All networked CLI commands and official SDK requests use the Gateway. Avoid building integrations against a service’s browser-facing or backend-private URLs; those routes are not a stable public contract.
Quick start
Section titled “Quick start”- Sign in to CHAMPREP and open API Keys.
- Create a key with only the scopes required by your integration.
- Store the key in a secret manager or operating-system keychain.
- Send a request to the production Gateway:
export CHAMPREP_TOKEN='replace-with-your-api-key'
curl --fail-with-body \ --header "Authorization: Bearer $CHAMPREP_TOKEN" \ https://api.champrep.com/v1/auth/whoamiThe response identifies the active account and credential context. Continue with authentication and API keys before adding service scopes.
Platform controls still apply
Section titled “Platform controls still apply”A valid key does not bypass the product controls that apply in CHAMPREP. A request can proceed only when all of the following are true:
- API Gateway access is enabled for the active plan and profile.
- The destination service is available to the active plan and organization.
- The key contains the scope required by the method and resource.
- The live per-minute, daily, and service-specific usage controls allow it.
- The active role is authorized to perform the operation in the destination service.
This is why an API key should be treated as an additional interface to the same account, not as a way around account, plan, role, or organization policy.