Skip to main content
POST
/
support
/
dsf
/
tickets
/
requested-data
curl --request POST \ --url https://panel.sendcloud.sc/api/v3/support/dsf/tickets/requested-data \ --header 'Authorization: Basic <encoded-value>' \ --header 'Content-Type: application/json' \ --data ' { "request_id": 144, "comment": "Sales invoice", "attachments": [ { "file_token": "4b08344f-8325-40df-8273-c0c31c412bb0" } ] } '
{
  "errors": [
    {
      "code": "bad_request",
      "detail": "Invalid JSON",
      "title": "Bad Request",
      "status": 400
    }
  ]
}
For the sales_data type, detailed sales data is expected, including item descriptions, quantities, prices, and tax rates. The data has to be passed as a valid JSON object under the sales_data key of the payload. A file object is expected for the following data_type’s: sales_invoice, purchase_invoice, confirmation_from_intended_receiver, declaration_non_receipt, pickup_receipt, recipient_id_scan, photo_of_parcel_exterior, photo_of_contents, photo_of_damage, photo_of_packaging_material_interior, photo_of_shipping_label, photo_of_parcel_weight, cn18_form, cn23_form, cn24_form, cp72_form, proof_of_delivery, proof_of_shipment, liability_statement, claim_letter, identity_card. Files are expected to be passed in the attachments array. Textual input is expected for iban_bic, cellphone, contact_person, correct_address, description_of_contents, description_of_damage, description_of_parcel, email_address data types. The info should be passed in the comment field. For the other type, textual input or file(s) can be expected depending on the title/description.

Authorizations

​
Authorization
string
header
required

Basic Authentication using API key and secrets is currently the main authentication mechanism.

Body

application/json
​
request_id
integer
required
​
comment
string | null
​
attachments
object[]
​
sales_data
object[]

Response

Data was uploaded successfully.