#1

Hi,

I am using new Twitter API v9 card endpoint like described here.
POST requests to create cards are good but I can’t find any info about cards update. I see card JSON model has updated_at field so it is not immutable. How can I update the card using Twitter v9 API?

Regards,
Mike Zub

#2

Thanks for the question, @michealzub. The new cards endpoints do not support updates. Is there anything else I can help with with regard to cards? Thanks!

#3

Thank you for the prompt response, @juanshishido! Is it OK to create a new card for each promoted Tweet update?

#4

Hello, @CMP! Yes, that is okay.

I am curious to know more about your workflow. Under what circumstances do you currently update a card? Do you have a sense of how many edits, on average, you make on a given card?

Thanks so much!

#5

Hi, @juanshishido! Our Ad model is different than yours: e.g. it contains the Ad state (enabled\disabled). So when our Ad model is updated it leads to a sequence of Twitter API calls. One of them was Twitter Website Card update call (executed on each Ad update), regardless were Card fields changed or not (Ad model state is uploaded as a whole, not as diff).

I don’t think Twitter Card related fields were needed to be updated (it was done because it was supported). So I will disable that update call to not create redundant Cards. But if the business requirements will change - I have to revert.

#6

Thanks for the context, @michealzub.

I don’t think Twitter Card related fields were needed to be updated (it was done because it was supported). So I will disable that update call to not create redundant Cards.

Sounds good. It’s best not to create redundant cards.