@juanshishido Thank you for the response.
@CMP: Thanks for the questions. From the params table:
A media_id of an image which will be used in this card. This is a write-only field. In response, the API will provide a Twitter URL for this image, that can be reused.
In other words, you must pass in a valid media_id for the image_media_id param, but you’ll see a Twitter URL, like the one you listed above.
It’s not obvious that the “media_id” clients provide will be expanded and returned in the “request.params.image” field of the response. It actually looks pretty unintuitive. Maybe specifying in the documentation the name of the field where the expanded url will be returned can make things clearer. A more predictable place to put it in would be within the “data” object in the response.
I don’t think you answered the question I asked, though:
My question is: is there a way to provide a pre-existing image URL to the POST cards/website endpoint instead of having to
re-upload an image (https://dev.twitter.com/rest/reference/post/media/upload is the endpoint I think I should be using for this) to satisfy the “image_media_id” requirement?
If my approach is completely wrong, please let me know what the preferred workflow is to create a Website Card.
