Hello,
I always get an Error while trying to create a Timeline Event with the API.
The Eventtype 1002382 exits.
I created the call as PUT with this payload {“id":“7f53cfe9-5453-44c3-92f8-978794d29330”,“eventTypeId”:“1002382”,“eventType”:“test”,“email”:"kontaktbooking@gmail.com”}
URL: https://api.hubapi.com/integrations/v1/213542/timeline/event
Result is always {“status”:“error”,“message”:“internal error”,“correlationId”:“76584e0a-39e2-4bff-8820-2dab85136b03”,“requestId”:“c2f0ce70-acfb-4b09-a9fc-9a3e43e3d582”}
Auth seems to be in place cause if i alter the bearer i get an authentication error.
The ids of the entities (appid,eventid) are correct like in upper example
The structure of the event should also be in place.
Any hint would be highly appreciated. The error message here is not really helpful
Hey @constantin1980,
When I install your app 213xxx on my own portal and tried to PUT a timeline event using the Create or update a timeline event endpoint with the following POST body:
{"id":"7f53cfe9-5453-44c3-92f8-978794d29330","eventTypeId":"1002382","eventType":"test","email":"kontaktbooking@gmail.com"}
and I was able to PUT it successfully.
Based on your error message it looks like a 500 internal server error. These errors are almost always transient delayed somewhere in the stack. In this case, could you retry these requests and see if it resolve your issue?
Hello
Its still not working
I redid connection with oauth to my portal id (7178964)
I tried
curl “https://api.hubapi.com/integrations/v1/213542/timeline/event” \
-X PUT \
-d “{“id":“62788492-f5c3-42c2-877b-e3aaa0f2b544”,“eventTypeId”:“1002382”,“eventType”:“test”,“email”:"kontaktbooking@gmail.com”}” \
-H “Authorization: Bearer secrettoken”
curl “https://api.hubapi.com/integrations/v1/213542/timeline/event” -X PUT -d “{“id":“62788492-f5c3-42c2-877b-e3aaa0f2b544”,“eventTypeId”:“1002382”,“eventType”:“test”,“email”:"kontaktbooking@gmail.com”}” -H “Authorization: Bearer secrettoken”
MY secret token i have removed her from the posts for sec reasons
Still the same results
Can there something wrong with my portal ?
Regards c
Hi, @constantin1980.
Like @WendyGoh, I installed your app in my account and was able to create a contact record with the same payload:
I made the actual PUT request within Postman.
Are you making the curl requests within your terminal?
If so, could you try making the requests in a REST client to see if you get a different response? If the request succeeds, we’ll know that the issue lies in your app or terminal environment.
It is not working with postman as well (same result)
I tried with 4 tools and the code (which integrates alot other systems ase)
Is there losg on your side to check ?
Can it be something in our portal ? (cause it works on yours)
Who could check that.
We really need to progress on that
Thx alot
Hi, @constantin1980.
You can actually view your app’s error log here in your developer account.
I see that your most recent failed requests have the header Content-Type: text/plain. Requests which failed earlier today have Content-Type: application/x-www-form-urlencoded.
Neither of these match what is defined in the documentation. Could you change the header to Content-Type: application/json and try again?
For comparison, the only headers I manually set in Postman are Content-Type: application/json and the Authorization header:
My Postman headers
My Postman body
