Create one reconstruction task from a batch of images of the space. Use the Argus Quickstart for upload code and the API Reference for request and response fields.
Keep gateway access tokens and task orchestration on your backend. Return temporary upload credentials only to the authenticated client performing the upload, and do not log them.
Step 1: Choose the input type
- Multiple 2:1 equirectangular panoramas.
- Multiple 1:1 pinhole images.
Choose one type for the entire batch.
Step 2: Prepare server-side access
Use a Team-owned Developer app and exchange its credentials for a gateway access token on your backend. Keep the app secret and gateway token out of browser bundles, URLs, logs, and support messages.
Follow Quickstart for authentication setup. Check both the HTTP response and gateway business result before continuing.
Step 3: Upload the selected batch
Package the selected images into one ZIP. Request temporary storage credentials with GET /open/v1/argus/file/token, upload the ZIP to the returned bucket under its permitted prefix, and retain the full uploaded object path. Follow Quickstart for input validation and upload code.
Submit the task after the selected batch has finished uploading. Keep temporary upload credentials limited to the authenticated upload operation.
Step 4: Submit reconstruction
Call POST /open/v1/argus/task/submit with the full ZIP object path in private_cos_keys and a nonempty title. A successful submission returns data.task_code; keep it for task-info queries. The API Reference defines the complete request and response.
Submission is not idempotent. If the response outcome is uncertain, confirm whether the task was created before submitting again; do not retry automatically.
Step 5: Query task information and handle the result
Query GET /open/v1/argus/task/info?task_code=... on your backend. After verifying gateway code is 0, handle data.status:
| Status | Action |
|---|---|
0 | Queued; query again later. |
1 | Processing; query again later. |
2 | Download the nonempty output_url before expiration_timestamp. |
3 | Stop and handle the failure reported in error_message. |
Validate the downloaded output.zip using Outputs and Result Handling, including the manifest's own success, partial, or error status. Store actual result files in controlled storage and discard the temporary download URL. Return only the result information your client needs, without exposing gateway tokens or raw diagnostics.
Pano-to-VR is a separate Pano-to-VR workflow with its own upload and task contract. Do not substitute that workflow's fields or packaging rules for the Argus batch upload.