1. Supported integration surface Eprecus supports documented versioned public API v3 endpoints, approved credentials, supported webhook events, and approved connector workflows.
2. Required case evidence Provide the endpoint or event name, HTTP method, safe request and response samples with secrets removed, UTC timestamp, trace ID, tenant context represented by the integration, and retry behavior.
3. Safe operation Use HTTPS destinations, scoped credentials, documented contracts, bounded retries, idempotency where required, and monitored delivery history. Rotate credentials through approved processes.
4. Delivery and retry Before retrying a failed webhook, import, or API mutation, confirm the earlier action did not complete. Support does not troubleshoot a destination that points to a private, local, metadata, or otherwise disallowed network address.