STEP 01
Choose a service
Use the API that owns the product data and workflow.
Developer platform
Build integrations against clear boundaries.
Discover production API surfaces, follow consistent authentication rules, and start integrations without guessing which product owns a capability.
TypeScriptomnia-client.ts
const response = await fetch(
"https://api.omniadigital.id/api/public/catalog",
{ headers: { "Accept": "application/json" } }
);
const catalog = await response.json();STEP 02
Authenticate
Send a bearer token for every protected operation.
STEP 03
Respect scope
Keep tenant, role, and product boundaries explicit.
Production directory
Fifteen APIs, grouped by responsibility.
Hostnames are public integration coordinates. Protected resources still require an authorized Omnia account and appropriate tenant permissions.
| Service | Group | Base URL | Transport |
|---|---|---|---|
| Core API | Platform | https://api.omniadigital.id/api | HTTPS |
| Platform API | Platform | https://api-platform.omniadigital.id/api | HTTPS |
| Education API | Education | https://api-education.omniadigital.id/api | HTTPS |
| Academic API | Education | https://api-academic.omniadigital.id/api | HTTPS |
| Fieldwork API | Education | https://api-fieldwork.omniadigital.id/api | HTTPS |
| LMS API | Education | https://api-lms.omniadigital.id/api | HTTPS |
| Bakery API | Food & Beverage | https://api-bakery.omniadigital.id/api | HTTPS |
| Cafe API | Food & Beverage | https://api-cafe.omniadigital.id/api | HTTPS |
| Cloud Kitchen API | Food & Beverage | https://api-cloud-kitchen.omniadigital.id/api | HTTPS |
| Food Court API | Food & Beverage | https://api-food-court.omniadigital.id/api | HTTPS |
| Clinic API | Industry | https://api-clinic.omniadigital.id/api | HTTPS |
| Church API | Industry | https://api-church.omniadigital.id/api | HTTPS |
| HRIS API | Industry | https://api-hris.omniadigital.id/api | HTTPS |
| Retail API | Industry | https://api-retail.omniadigital.id/api | HTTPS |
| Social Commerce API | Industry | https://api-social-commerce.omniadigital.id/api | HTTPS |
Request convention
A small, predictable request surface.
Use JSON over HTTPS, identify the authenticated account with a bearer token, and send tenant context only where the product requires it.
- Never expose tokens in browser URLs or logs.
- Treat 401 as an authentication failure and 403 as insufficient permission.
- Retry only idempotent operations after transient 5xx responses.
- Keep production and test credentials completely separate.
Example request
curl "https://api.omniadigital.id/api/auth/me" \
-H "Accept: application/json" \
-H "Authorization: Bearer $OMNIA_TOKEN"Expected authenticated response
{
"account": { "id": "…" },
"permissions": ["…"],
"tenant": { "id": "…" }
}Need platform access?