Uploading data to TON API fails using PHP cURL

[hector_borras]

Anyway it would be good if this documentation will be updated about a mandatory oauth_body_hash in tailored audiences upload.

https://dev.twitter.com/rest/ton/single-chunk

https://dev.twitter.com/rest/ton/resumable

[Blackburn29]

@JBabichJapan @hector_borras @majoritasdev reviving this since I’m having new issues.

I can successfully upload files via the single chunk upload API, however when issuing multi-chunk requests, I am getting 400 error responses AFTER initialization when trying to upload the first chunk.

Heres an example of my request:

PUT /1.1/ton/bucket/ta_partner/340083909/nHbzAQ6zrmIp9FY?resumable=true&resumeId=317889 HTTP/1.1
Expect: 100-Continue
User-Agent: GuzzleHttp/6.2.0 curl/7.35.0 PHP/7.0.8-4+deb.sury.org~trusty+1
Host: ton.twitter.com
Content-Type: text/comma-separated-values
Content-Range: bytes 0-1048575/32500000
oauth_body_hash: YmZiYzRiYTRjYTdlMmFhODEyMDFmMjhjNzkyZDMwZmRkZTQyMTgxZg==
Authorization: OAuth oauth_consumer_key=“X”, oauth_nonce=“cbc3c62f4826a1fa5257bc243f9953b32056a9c0”, oauth_signature=“ksSBxG3PrOXGnxOgOjyLIeG7mzY%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1468873554”, oauth_token=“X”, oauth_version="1.0"
Content-Length: 1048576

< HTTP/1.1 100 Continue

• We are completely uploaded and fine
  < HTTP/1.1 400 Bad Request

I have compared my headers to the values of the ton_upload ruby script and they are an exact match…
(I also include the oauth_body_hash as mentioned above)

Uploading file in multiple chunks…
Uploading chunk 1 (0-1048575/32500000)…
{“Content-Type”=>“text/comma-separated-values”, “Content-Length”=>1048576, “Content-Range”=>“bytes 0-1048575/32500000”}

Any ideas here?

[hector_borras]

Hey @Blackburn29, don’t worry.

I made a lot of improvements today and now I’m able to upload chunked files too!!!

I need to check if the list that I’ve uploaded one hour ago is correct (waiting for Twitter process) And after that I can push the branch.

Thanks!!!

[Blackburn29]

@hector_borras do you mind explaining what you did differently for chunked files vs single uploads? I’m testing some stuff out on my own code base for this using Guzzle and would like to at least have an understanding of what I’m doing wrong.

[hector_borras]

First of all, I don’t use Guzzle, I make raw cURL requests.

I think your problem is with oauth_body_hash, it should be insidhe the Authorization header like oauth_signature or oauth_version

[Blackburn29]

I dont think that is the problem since single-chunk uploads work just fine.

[Blackburn29]

@hector_borras just to test, I added oauth_body_hash to the Authorization header and I still get the same 400 response.

[Blackburn29]

I found my issue. The docs give an incorrect ‘Location’ response. It claims location to be:

/1.1/ton/bucket/{bucket}/SzFxGfAg_Zj.mp4?resumable=true&resumeId=28401873

however from testing, ive found that this can vary. Most of my location URLs contain “data” instead of “bucket” in the URL

This needs to be updated in the docs…

[hector_borras]

Finally I have the TA uploaded.This afternoon I’ll try to update the lib with clean code and How to upload TA.

[divireizdivi]

Hi guys,

I’m also having hard time uploading tailored audiences to Twitter TON. Getting the same 403 Forbidden.

Could you please explain, what the $contents variable is in your example ('oauth_body_hash' => base64_encode(sha1($content));)? Can’t seem to find anywhere information about oauth_body_hash… such a poor documentation for plain PHP…

[Jhon_Pierre]

Hey Hector! I am a .Net developer, I am trying to upload a CSV file to a Tailored Audience with the list of phone numbers, And it is happening the same error here, I am making the POST and getting first the 400 Bad Request and then the 403 Forbidden…
So I am looking to your answer, and I have a couple of questions, cuz I see you got the EUREKA!

• What is this new oauth_body_hash header?
• What should be the value I have to set to it?
• Does this affect the oauth_signature?
• We need to include this inside the Authorization header?
• So you hashed your body data to post?

I really appreciate your answer.

Regards,

[hector_borras]

Sorry I didn’t see this answer. If you check my lib:

hborras/twitter-php-ads-sdk

You will see how to implement it!

[deansharedemo]

Hi @hector_borras, Please review Php sdk issue