Timeline API Article is Now Available!

@darkknight Job got completed with the below error , hence the activity data is not updated.

[{"errorCode":"GS_TL_10_0204","message":"Activity identifier key not provided"}]}

Please provide activityId for the key “Gsid” as part of the payload.

@smitha bhanoori why didn’t that error message come through on my side during the test? I shouldn’t have to rely on reaching out to Gainsight to understand why it didn’t go through.
 

Also, I am using the ActivityId, but the documentation isn’t very clear on exact format or JSON config.  Perhaps we can schedule a call to walk through this?

@darkknight  Please use the job Id received in the response as the input for for Status API to know the result. In documentation it is already mentioned that we can either use External Id or activity Id. Sure, we can have a call.

@smitha bhanoori I should clarify, I’m attempting to do this via External Actions (not via custom code), which I have done successfully using other APIs (CTA, Company) and haven’t had this much trouble.  

 

Having similar issues.

Request id:     37bbb4bf-4e02-4cde-8bb7-8dda40ec26af

@Wayne Please use the url as “activity/bulk?identifier=externalid” .

Angular braces are mentioned to represent the placeholder.

Maybe a good idea would be to have examples of a URL as it would appear when it is configured?

Assuming these aren’t lingering technical problems with the API, it seems like most of this back and forth could have been avoided with clear end-to-end examples of the whole process (once PUT was enabled that is).

I haven’t worked much with the API, and I can tell you that having that level of technical detail would be useful for me but also having a full example to reverse engineer for troubleshooting is equally helpful even if you’re an API pro, when a new API feature comes out.

Still erroring out,

Request id: d17667a0-fa9f-48c2-a10e-10c61db289fa

@Wayne We are not observing this request from our end. Can you please share more details on the issue.

Hey @smitha bhanoori I figured out that issue.

It was because I am trying to send a date time. I defined the format my data is in, yyyy-MM-dd'T'HH:mm:ssZ. However, Timeline APIT is still expecting it in, yyyy-MM-dd'T'HH:mm:ss.SSSZ

I’ve built a workaround for this. Now I am to the point where we have the same timeline type name across multiple relationship types and I need to define the type name id instead of type name and have no way to do this en masse.