About unavailabilities and availabilities

[Heitor Danilo]

Hi,

I am currently working on creating an endpoint that creates unavailability for the easy!appointments API. Here is an example request:

"

{

  start: "2023-02-22 09:00:00",

  end: "2023-02-22 11:00:00",

  location: 'Test Street 1A, 12345 Some State, Some Place',

  notes: "This is a test appointment.",

  providerId: specialist.providerId

}

"

This is the response I receive:
"
{
  status: 201,
  data: {
    id: 132,
    book: '2023-02-19 21:09:18',
    start: '2023-02-22 09:00:00',
    end: '2023-02-22 11:00:00',
    hash: 'U6s4eL2tvmgB',
    location: 'Test Street 1A, 12345 Some State, Some Place',
    notes: 'This is a test appointment.',
    providerId: 126,
    googleCalendarId: null
  },
  error: {}
}"

However, when I call the availability endpoint from this date, I receive the following response:
[
  '09:00', '09:15', '09:30',
  '09:45', '10:00', '10:15',

  '10:30', '10:45', '11:00',

  '11:15', '11:30', '13:00',
  '13:15', '13:30', '13:45',
  '14:00', '14:15', '14:30',
  '14:45', '15:00', '15:15',
  '15:30', '15:45', '16:00',
  '16:15', '16:30'
]
It seems that the API is returning available time slots that include the unavailability that I created. Is this the expected behavior?

[Alex Tselegidis]

Hello! 

Did you provide the same provider ID when trying to get the availabilities? 

If not the app might offer you available time of other providers as well. 

Alex Tselegidis, Easy!Appointments Creator
Need a customization? Get a free quote!