The Eprecus public REST API is the supported integration surface for approved external systems.
Build integrations safely Use a purpose-specific API key or approved authentication flow, keep credentials in a secret vault, and request only the scopes required by the integration. Always use the documented API version and send complete validated payloads.
Read-only discovery request ```http GET /eprecus-erp/api/v3/public/support/knowledge?query=payroll HTTP/1.1 Host: api.eprecus.com Accept: application/json ```
Expected response shape ```json { "items": [ { "slug": "payroll-and-hr-foundations", "title": "Payroll and HR foundations" } ] } ```
Protect tenant boundaries An integration must operate only within the tenant context and permissions assigned to its credentials. Do not reuse production credentials in development, expose credentials in client-side code, or infer access to another organization.
Authenticated request pattern ```http GET /eprecus-erp/api/v3/{approved-endpoint} HTTP/1.1 Host: api.eprecus.com Authorization: Bearer {short-lived-access-token} Accept: application/json X-Tenant-Id: {assigned-tenant-id} ```
Operate webhooks reliably Use an HTTPS destination, validate delivery signatures where available, return an appropriate response promptly, and monitor delivery history. When a request or webhook fails, search the exact Eprecus error code and retain the trace ID for support.