Skip to main content

Upload a support-config CSV

This guide covers loading the support configuration — the mapping of required documents per provider product code — through the asynchronous CSV upload.

Prerequisites​

  • Credentials enabled for support-config upload (the same permission lets you poll the process).
  • A CSV file (text/csv), up to 25 MB, with the required header columns.

Step 1 — Upload the CSV​

curl -X POST https://sandbox.osigu.com/pre-attendance-api/v1/checkin/support-configs/upload \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -F 'file=@support-config.csv;type=text/csv'

The provider is taken from your token, not from the file. The CSV is validated synchronously (MIME type and header columns) before anything is stored; if that fails you get 400 with no side effects.

On success you get 202 Accepted with a process_id:

{ "process_id": "3f2504e0-4f89-41d3-9a0c-0305e82c3301" }

Step 2 — Poll the process​

curl https://sandbox.osigu.com/pre-attendance-api/v1/checkin/support-configs/process/$PROCESS_ID \
  -H "Authorization: Bearer $ACCESS_TOKEN"

The response carries the current status and metrics, plus errors_file_url — a presigned link to a validation-errors CSV, or null if every row was valid. Poll until the process reaches a terminal status.

Partial success is normal

Parsing is per-row: valid rows are upserted even if others fail. A finished process with a non-null errors_file_url means some rows were rejected — the valid ones still applied.

Step 3 — Download row errors (if any)​

curl https://sandbox.osigu.com/pre-attendance-api/v1/checkin/support-configs/process/$PROCESS_ID/errors \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -o validation_errors.csv

Returns the errors as a text/csv attachment. Fix the flagged rows and re-upload just those (the upsert is idempotent per product code).

What happens behind the scenes​

Next steps​