SDTing via API, one source work the other does not

Well shoot, you can't pick more than one solution. The Action in Jira is working now! I can set a 1 hour SDT on a specific device!  plus I can remove the 4 steps I had to calculate epoch in milliseconds because duration works. However I do have to add a step to GET the ID integer of the device. Either way though, it's working. Thank you guys!

According to the swagger for v3, the type fields is actually "sdtType":

{
timezone	string
example: America/Los_Angeles
The specific timezone for SDT

sdtType	string
example: oneTime
The type of sdt. The values can be oneTime|weekly|monthly|daily|monthlyByWeek

monthDay	integer($int32)
example: 7
The values can be 1 | 2....| 31. Specifies the day of the month that the SDT will be active for a monthly SDT

weekOfMonth	string
example: 1
The week of the month that the SDT will be active for a monthly SDT

endDateTime	integer($int64)
example: 1534554000000
The epoch time, in milliseconds, that the SDT will end

type*	string
example: ResourceGroupSDT
The type of resource that this SDT is for. The values can be CollectorSDT | DeviceDataSourceInstanceSDT | DeviceBatchJobSDT | DeviceClusterAlertDefSDT | DeviceDataSourceInstanceGroupSDT | DeviceDataSourceSDT | DeviceEventSourceSDT | ResourceGroupSDT | ResourceSDT | WebsiteCheckpointSDT | WebsiteGroupSDT | WebsiteSDT | DeviceLogPipeLineResourceSDT

minute	integer($int32)
example: 6
The values can be 1 | 2....| 60. Specifies the minute of the hour that the SDT should begin for a repeating SDT

duration	integer($int32)
example: 138
The duration of the SDT in minutes

endHour	integer($int32)
example: 5
The values can be 1 | 2....| 24. Specifies the hour that the SDT ends for a repeating SDT

startDateTime	integer($int64)
example: 1534460400000
The epoch time, in milliseconds, that the SDT will start

hour	integer($int32)
example: 3
The values can be 1 | 2....| 24. Specifies the hour that the SDT will start for a repeating SDT (daily, weekly, or monthly)

weekDay	string
example: Sunday
The week day of sdt. The values can be SUNDAY|MONDAY|TUESDAY|WEDNESDAY|THURSDAY|FRIDAY|SATURDAY

comment	string
example: Emergency prod deployment
The notes associated with the SDT

endMinute	integer($int32)
example: 18
The values can be 1 | 2....| 60. Specifies the minute of the hour that the SDT ends for a repeating SDT

}

Yup.. but I get the feeling I was using a V1/2 body content. Reading here under SDTs I'm seeing many more possible fields. 

Is Jira putting the sdt time in milliseconds or seconds? LM won't take seconds.

Yessir.. MS in postman and Jira. When I say I tested them identically I meant like identical twins sort of identical :)

? What is this signature thing you speak of? I don;t have/am not using a pre-request script in Postman. Sounds like there might be a part of this I missed..

Sorry, that was sarcasm above. lol.  I was trying to be funny, but seriously no I have no idea about any script or sig needed.

Crap sorry again.. no the 400 is a 'Bad Request'. So it sounds like improper formatting, incorrect field names/values. But I just compared again to a webhooks.sites and it's being sent accurate info.

Teh raw content is (slightly sanitized):

{ "type": "DeviceSDT", "sdtType": 1, "comment": "Device SDT'd by Ben Hart", "deviceDisplayName": "lbextd01.domain.net", "startDateTime": 1715091972832, "endDateTime": 1715095572832 }

Well, it depends on whether you're using an API id/key or a bearer token. If you're using api id/key, then you have to generate a signature based on the verb, endpoint, current time, and payload (if any). If you're not doing that, it might be why jira is getting the 400.

If you're using a bearer token, it's much simpler. However, they're newer and not many have started using them.

Oh yeah.. I'm using a bearer token in both cases.