Provider organization: ManTech
Authentication
How developers authenticate ManTech APIs: Firebase console login, phone OTP sign-up and sign-in, application TEST keys (mantech_test_…), and optional /api/v1/auth JWT routes. Public IFSC, GST, HSN, and SAC calls use the Console Bearer key. Phone verification is Firebase Identity Toolkit. OAuth client credentials are not yet deployed.
Authentication
Create a TEST key in the Developer Console. Send Authorization: Bearer on mantechstudio.in/api/v1.
Capabilities
- TEST API keys
- Firebase console login
- Email and phone OTP sign-in
Known limitations
- OAuth client credentials are not deployed.
- Console keys do not authenticate /external/v1 or /api/v1/auth.
- Phone OTP requires an E.164 number and a reCAPTCHA token. This API does not store the code.
- LIVE keys are gated — TEST is not production access.
Endpoints
- POST/api/v1/auth/signup
- POST/api/v1/auth/login
- POST/api/v1/auth/refresh
- POST/api/v1/auth/password-reset
- POST/api/v1/auth/logout
- POST/api/v1/auth/phone/send-otp
- POST/api/v1/auth/phone/verify-otp
Access and quota
TEST · TEST
1,000 requests per UTC day per application + environment (shared across certified /api/v1 families)
Burst limiter plus daily quota. TEST is not unlimited.
Production · LIVE
Not a self-serve checkout. Request production access.
Not published as a public SLA.
There is no self-serve checkout. Production access is request-only. TEST keys are not production access. Quota is enforced by the gateway per application + environment, not by this page.
Gateway
Developer API keys stay on the gateway and are not the credential for these routes. Public POST /api/v1/auth/{signup,login,refresh,password-reset,logout,phone/send-otp,phone/verify-otp} is an allowlist. The gateway calls ManTech API Platform /external/v1/auth with Google OIDC. Logout also requires the end-user Firebase ID token. Website sign-in UI does not use this product.