クラシックファイルタイプは2021年1月をもって使用できなくなりました。クラシックファイルを移行することも、PDFをダウンロードすることもできます。詳細はこちら

Help with API sample upload

回答済み
デモをリクエスト
  • 編集済み

Hello. I am trying to upload a text file as a test sample. I have tried every version I can think of and keep getting the same 404 not found. Here is my code.

 curl -v -X POST -H 'Content-Type: application/json' -H 'Accept: application/json' -H "Authorization: Bearer $token"  "https://api.app.wdesk.com/platform/v1/testForms/$form_id/testPhases/$phase_id/matrices/$matrix_id/samples/$sample_id/attachmentsUpload" -d '{"fileName": "out2"}'

I know that my token,form_id,phase_id,matrix_id, and sample_id are correct as I can run a get with the same url /attachments and it shows me current attachments. The API documentation says it should be attachmentUpload but it errors without the s like attachmentsUpload. I know that the attachment out2 is found because changing the name returns a file not found error. I have also tried using -F file=@out2 instead of -d. 

Here is the verbose output with my bearer token cut off. Can anyone tell me what I am doing wrong?

 curl -v -X POST -H 'Content-Type: application/json' -H 'Accept: applicatioom/platform/v1/testForms/$form_id/testPhases/$phase_id/matrices/$matrix_id/samples/$sample_id/attachmentsUplo
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 108.156.224.124:443...
* Connected to api.app.wdesk.com (108.156.224.124) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=api.app.wdesk.com
*  start date: Feb 22 00:00:00 2023 GMT
*  expire date: Aug 26 23:59:59 2023 GMT
*  subjectAltName: host "api.app.wdesk.com" matched cert's "api.app.wdesk.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
*  SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> POST /platform/v1/testForms/f68941b5-f1e3-4adf-a245-7fc7cb3ae77e/testPhases/baaf65d4-2ae5-412f-9ed8-159a54dd-e185-4504-b26b-e28eaed6d4be/attachmentsUpload HTTP/1.1
> Host: api.app.wdesk.com
> User-Agent: curl/7.81.0
> Content-Type: application/json
> Accept: application/json
> Authorization: Bearer eyJhJVWhUFNinS7de5gtzbqWqp9jNi77OH7IQ
> Content-Length: 20
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Content-Type: application/json
< Content-Length: 0
< Connection: keep-alive
< Date: Thu, 01 Jun 2023 00:24:15 GMT
< x-amzn-RequestId: bb9d6f10-44c0-4385-839d-80f30df3b74a
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< x-amz-apigw-id: F0C_aHIgoAMFvYQ=
< X-Cache: Error from cloudfront
< Via: 1.1 01b6d83a9b2cdd6c2a5f42b34f1e78dc.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: DFW56-P4
< X-Amz-Cf-Id: cYROD00OZ79RomcTBNaJe1UfaGSYO04_ki0khGnvnZabcLbNu6wF3w==
<
* Connection #0 to host api.app.wdesk.com left intact

 

0

コメント

7件のコメント

日付 投票

サインインしてコメントを残してください。