The Supported Activity Hierarchies chart indicates what an activity can be connected to e.g. create a contact, then you can attach a call log to the contact, then you can attach a comment to the call log, but you could not connect a comment to a contact.

When creating any type of activity you must provide the PARENT parameter.  This indicates what the activity you are creating should be connected to e.g. when creating a call log specify the contact’s ID as the parent, when creating the comment specify the call log’s ID as the parent.

When you create an item the response includes the ID of the newly created item.  This makes it easier to create a chain of related items without having to search for the IDs.

Thanks! This is perfect, and a simple explanation.

I had intuitively figured this out, but my code was breaking so I thought I was doing it wrong.

Turns out I was using <data>text</posttext></data> which it didn’t like. I guess you only name the fields when there is more than one field posting?

Anyhow, I’m getting the hang of this. I can’t wait to get my top secret prototype working so I can share it with you guys

But, alas, I did something wrong.

The comment showed up like: “undefined wrote:“

So what did I miss? Clearly there is a logic behind which fields are required for which types of activities, but in the documentation is only says “posttext” is required.

Looking at another post there was also “postuser” and “postdate”. Shouldn’t these be implied by the credentials and time of a comment being posted to the API?

Can you point me at a more comprehensive reference for decoding and grokking the API? Or just slap me silly so it all makes sense? :p

Thanks!

Here is what I used here:

The user’s name did appear correctly.  If it doesn’t show the same for you please send our support team the exact command your using so they can verify check the configuration of the account that is authenticating and see what’s happening.