put https://api.accelevents.com/rest/event//people//schedule/
Attendee can update the meeting schedule which is already created by them.
Here is the description of response attributes, which returns in the form of JSON.
| Attributes | Description |
|---|---|
| eventId | It's contain eventId which has attendee scheduled meeting for this event. |
| exhibitorId | It's contain exhibitorId when attendee schedule meeting with exhibitor company representatives. |
| id | This should be meeting schedule unique id. |
| meetingEndTime | This should be meeting end time which attendee want to schedule. |
| meetingStartTime | This should be meeting start time which attendee want to schedule. |
| note | This is note to attendee set. |
| origin | It's contain to meeting created from where. Possible values are PEOPLE_PAGE, EXPO_COMP_REPRESENTATIVE, USER_PROFILE, CHAT. |
| receiverUserId | This contain receiver user id. |
| rejectedBy | This contain user id who has rejected meeting schedule. |
| senderUserId | This contain sender user id. |
| status | This will suggest meeting status. Possible value are CREATED, BOOKED, DECLINED, CANCEL. |
| createdAt | Return meeting schedule created datetime. |
| updatedAt | Return meeting schedule last updated datetime. |
Here is the possible error messages, which return if any condition gets failed or required data is missing for processing.
| Error Code | Error Description |
|---|---|
| 200 | OK |
| 403 | Accessing the resource you were trying to reach is forbidden. |
| 404 | The resource you were trying to reach is not found. |
| 40600013 | Cant create url |
| 4040200 | Event Not Found. |
| 4068001 | Attendee Not Found. |
| 4070002 | Meeting schedule slot not available. |