Kenny_Elkington

It's because of the usage of the createOnly action. createOnly will only work when the key is unambiguous. It will work fine if you use createDuplicate, or if you use a different unique key.

Munchkin API uses the SOAP API names for fields, not the REST API names. You're using the REST ones, so your call will end up failing.

This is typically done by support. I would reopen the case.

This won't work for emails, since Javascript doesn't work inside of almost all mail clients, but twitter has a few native capabilities for this here: Embedded Timelines | Twitter Developers That litmus email, looks to be using some CSS wizardry that overwrites the content properties of some containe...

The only thing I could think of is if you're using MME and sent a push notification to the user's phone. Other than that, there's no native functionality for sending SMS or MMS, those capabilities are only provided through Launchpoint partners and Webhooks.

I responded on StackOverflow as well, but could you provide what exactly you're posting? You can just add some debug statements inside the postData for $url and $this->content? Please redact your access token as well.

Does the client have workspaces and partitions enabled for their subscription? If so, your API user may be missing an appropriate role in the desired workspace. Do you have any of the filter params set?

Are you getting a paging token in the response? It's very possible that the campaign just isn't in the first page of results.

My guess would be your getting packets dropped at the load-balancer, your test is running through 700 update requests in basically however fast your machine can accomplish it. If you added some throttling to a maximum of 15 concurrent requests, then I would expect you would stop seeing this.

datetime expects ISO 8601 datetime strings, so you need to follow the yyyy-MM-ddThh:mm:ssz format/