Use case / Subcontractor dispatch
Webhooks / Inbound
Use case / Document import
External Document Update With Payload
Upload a document to a specific stop on a subcontracted trip.
This webhook uses Basic Auth (webhook credentials), not the OAuth credentials used for the API. Contact integrations@qargo.com to request credentials.
Query parameters
| Parameter | Required | Description |
|---|---|---|
| question_path_key | Yes | Maps the file to a document type in Qargo (e.g. CMR, POD, WEIGHT_NOTE) |
| stop_id | Yes | The Qargo UUID of the stop to attach the document to |
Headers
| Header | Required | Description |
|---|---|---|
| Content-Type | Yes | MIME type of the file (e.g. application/pdf, image/jpeg) |
| Content-Disposition | No | Provides the filename: attachment; filename="POD.pdf" |
Filename handling
The uploaded file's name in Qargo is determined by:
- If Content-Disposition includes a filename — that value is used, combined with the question path key default. For example: filename="pod1234.pdf" with question path key default POD.pdf → stored as pod1234_POD.pdf.
- If no Content-Disposition is provided — the default filename from the question path key configuration is used.
Example
curl -X POST \
"https://api.qargo.com/v1/webhook/subco-document-upload\
?question_path_key=POD&stop_id=<stop_uuid>" \
-u "<webhook_client_id>:<webhook_secret_id>" \
-H "Content-Type: application/pdf" \
-H "Content-Disposition: attachment; filename=POD.pdf" \
--data-binary @/path/to/document.pdf
post/v1/webhook/subco-document-upload
Query parameters
question_path_keystring required
The question path key to map the file in Qargo, for example: CMR/POD
stop_idstring required
The stop ID to which the document is related
Request body
Response
Successful Response
{"stackTrail":"paths:/v1/webhook/subco-document-upload:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}
Changes
No recorded changes to this endpoint across all 1 revision of this API.