Server request pattern
const response = await fetch(`${origin}/knowledge/facts`, {
headers: { Authorization: `Bearer ${token}` },
signal: AbortSignal.timeout(5000)
});Build on explicit contracts
Documentation
Explore the provider-neutral concepts for connecting governed requests, responses, evidence, and operational outcomes.
CONTRACT WORKBENCHSERVER → SALERINGO
GET
/knowledge/facts- Runtime
- server only
- Timeout
- bounded
- Workspace
- explicit
- Correlation
- retained
Build a server-side connection whose scope and failure behavior are visible.
IMPLEMENTATION OUTCOME
Build a server-side connection whose scope and failure behavior are visible.
The published contract is normative. Examples explain the pattern and do not grant an operation or credential.
- 1 · Keep credentials server-sideLoad the supplied credential from a secret store, never from browser code.
- 2 · Bind the workspaceUse the workspace context approved for the customer and operation.
- 3 · Set a timeoutBound every provider call and do not silently convert a timeout into success.
- 4 · Record correlationStore the Saleringo request ID beside a non-sensitive local correlation ID.
REQUEST → RESULT
Keep the request, result, and evidence together.
Outcome branch
if (!response.ok) {
const failure = await decodeFailure(response);
return handleByStatus(failure);
}RECOVERY CONTRACT
A retry is not the answer to every failure.
StatusMeaningClient action
401Credential is missing, expired, or invalidStop; refresh through the approved server flow.
403Identity lacks the exact permission or scopeDo not retry; request an access review.
409State, version, idempotency, or approval conflictsRead the conflict and reconcile before another command.
422The request does not match the published schemaCorrect the named fields; do not retry unchanged.
429The integration is sending too quicklyHonor the supplied wait guidance and apply backoff.
5xxA temporary service failure may have occurredPreserve IDs; retry only when the operation permits it.
IMPLEMENTATION SUPPORT
Bring one operation. Leave with the next test your team can run.
Do not send credentials, customer secrets, or raw payment data. Include the contract version, environment, operation, timestamp, and non-sensitive correlation ID.