I'm trying to use the Blue Jeans api sdk c#.

Hello Mike,

May I ask what the value of t1 is being inputted as? Also, may I ask if you've tried using seconds for t1 instead of milliseconds from epoch. Seconds from epoch would fit in an Int32 type. And if it does go through, I can confirm the date that appears in our side to check if it's inaccurate.

Best regards,

Alphi Villanueva

Hi Alphi,
I tried putting in int32 values using seconds from epoch. I still got the error:
"JSON integer 1538987592000 is too large or small for an Int32. Path '[0].start', line 1, position 109." No meetings were scheduled.


I then tried changing the class 'ScheduleMeetingMinComp' to accept longs. This works to some extent. I can create new meetings that show up in 'https://bluejeans.com/scheduling/' with the expected values. However, I still get error messages eg: JSON integer 1538990732757 is too large or small for an Int32. Path 'start', line 1, position 142.

What was intersting, is that afterwards I tried something else:
  try
            {
                var result = apiMeeting.ListMeetings(userId);
            }
            catch (Exception e)
            {
                Debug.Print("Exception when calling     apiMeeting.listMeeting: " + e.Message);
            }

This returns an error of JSON integer 1538987592000 is too large or small for an Int32. Path '[0].start', line 1, position 109.

On this ocasion I'm not even sending anything beyond my userId

Hello Mike,

That number you used seems to still be miliiseconds from epoch, perhaps trying 1538987592 instead which is an Int32 value.

Best regards,

Alphi

Hi,
I did try using int32 values but this resulted in  JSON integer 1538987592000 is too large or small for an Int32. I get an error whether I use an int32 or a long.

Also I have tried this:
var result = apiMeeting.ListMeetings(userId);


This does not return my list but instead also returns an error of JSON integer 1538987592000 is too large or small for an Int32. Path '[0].start', line 1, position 109.

Thanks,
Mike

Also I should point out that the documentation gives this:-

Start int? A UNIX Timestamp in milliseconds

A A UNIX Timestamp in milliseconds for a current date will always be a long.