Integration guide
Build a server-side connection whose scope and failure behavior are visible.
Start with one customer action, then define authentication, workspace scope, permission, request identity, retries, errors, evidence, and the owner of unresolved work.
Implementation checklist
Keep credentials server-side
Load the supplied credential from a secret store, never from browser code.
Bind the workspace
Use the workspace context approved for the customer and operation.
Set a timeout
Bound every provider call and do not silently convert a timeout into success.
Record correlation
Store the Saleringo request ID beside a non-sensitive local correlation ID.
Request and result
const response = await fetch(`${origin}/knowledge/facts`, {
headers: { Authorization: `Bearer ${token}` },
signal: AbortSignal.timeout(5000)
});if (!response.ok) {
const failure = await decodeFailure(response);
return handleByStatus(failure);
}Failure handling
| Status | Meaning | Client action |
|---|---|---|
| 401 | Credential is missing, expired, or invalid | Stop; refresh through the approved server flow. |
| 403 | Identity lacks the exact permission or scope | Do not retry; request an access review. |
| 409 | State, version, idempotency, or approval conflicts | Read the conflict and reconcile before another command. |
| 422 | The request does not match the published schema | Correct the named fields; do not retry unchanged. |
| 429 | The integration is sending too quickly | Honor the supplied wait guidance and apply backoff. |
| 5xx | A temporary service failure may have occurred | Preserve IDs; retry only when the operation permits it. |
Implementation support
Do not send credentials, customer secrets, or raw payment data. Include the contract version, environment, operation, timestamp, and non-sensitive correlation ID.