Skip to main content

​
Should we start in sandbox or production?

Start in sandbox. It lets you validate your workflow safely before you move any live traffic into production.

​
What is the fastest path to a successful first submission?

Follow the Quickstart. It covers the narrowest end-to-end happy path from create to completed submission attempt.

​
What does submissionAttempt.status = completed mean?

It means Collate successfully delivered the request to the payer destination. It does not mean the payer approved the request. Use the authorization state, actions, artifacts, and timeline to follow the rest of the payer lifecycle.

​
Why can a case be ready to preview but not ready to submit?

Preview checks whether the current packet is ready to submit and renders the latest output. It does not start submission processing.

​
How do we know which documents are required?

Check requirements.documents on the authorization. Required items appear there and should be attached before you submit.

​
Can hidden branch answers cause problems?

No additional cleanup is required on your side. Collate removes stale answers from hidden questionnaire branches automatically.

​
How do we simulate approvals, denials, or payer requests for information?

Use the sandbox test-ingress flow documented in Sandbox testing.

​
Which public resources should integrators expect to work with most often?

Most integrations primarily use:
  • authorizations
  • submission attempts
  • files
  • actions
  • artifacts
  • timeline entries
See Introduction for the high-level model.

​
Where should we look first during an issue?

Start with:
  1. the authorization’s current workflowState and decisionState
  2. the requirements object
  3. the latest submission attempt, if one exists
  4. the authorization timeline

​
How is live customer support handled?

For active deployments, Collate support is coordinated through the support contact provided during onboarding. See Support process for what information to include when asking for help.