[#1442] API 404 & 500 Errors on POST /panel/api/event - Request Developer Assistance

Bug Reports
,
1

Migrated from Redmine #1442 | Author: Marc Fowler
Status: New | Priority: Immediate, there is BUG! | Created: 2025-07-19

Hi SimplyMeet Dev Support,

Despite following all SM API Dev documentation, I’m still getting persistent API 404 or 500 errors - and I’d appreciate your assistance in resolving this.

Just to clarify, I was on a free trial until yesterday - but I don’t want you to assume this API issue is related to that. It was happening before the trial expired.

I’m still learning API-based automation and coding, so thank you in advance for your patience!

Booking Endpoint I’m Using

POST https://secure.simplymeet.me/panel/api/event

Headers I’m Sending

Key Value

X-API-KEY:
Accept: application/json
Content-Type: application/json

Raw JSON Body (sent as raw JSON)

{
“eventTypeId”: 248556,
“name”: “Marc Test”,
“email”: “test@example.com”,
“startTime”: “2025-07-21T14:00:00+10:00”
}

Troubleshooting Already Performed:

Confirmed eventTypeId is valid.

API key tested at /panel/api/api-key and confirmed active.

Time slot manually bookable via public SimplyMeet link.

JSON is well-formed and sent as raw, not form-data.

All Postman auto-headers disabled or removed (when possible in Postman).

Verified ISO 8601 timestamp with UTC offset.

Tried multiple browsers, Postman environments, and deployment contexts.

Current Result:

POST /panel/api/event consistently returns either:

404 Not Found

or 500 Internal Server Error

Yet GET /panel/api/event-type/availability/248556?startDate=…&endDate=… works perfectly

Possibly Related Support Case:

I’ve attached a PDF showing another developer (Ticket #1243, June 2024) encountered the exact same issue with this endpoint — and your team simply replied:

“fixed.”

Could this be another instance of that backend issue? If so, could you please re-check the eventTypeId config or the service backend linked to my account?

Request for Help:

I’d love to get this working for production use ASAP. If there’s a feature toggle, configuration quirk, or hidden field issue behind the scenes - I’d really appreciate your guidance. I’m learning this as I go, and your help has been amazing so far.

Warm regards,
Marc Fowler

2

Marc Fowler wrote:

19/07/2025 @ 11:15am AEST: I have now upgraded to paid SimplyMeet Professional monthly account.

3

Nicholas Alias wrote:

Hello

Please use this documentation. It requires passing different parameters.

4

Marc Fowler wrote:

Nicholas Alias wrote in #note-3:

Hello

API documentation | SimplyMeet.me Online Scheduling

Please use this documentation. It requires passing different parameters.

API documentation | SimplyMeet.me Online Scheduling

Nicholas Alias wrote in #note-3:

Hello

API documentation | SimplyMeet.me Online Scheduling

Please use this documentation. It requires passing different parameters.

API documentation | SimplyMeet.me Online Scheduling

Hi Nicholas,

Can you please provide clearer support and instructions?

As I mentioned in my original submission - not only am I relatively new to this - but I have already followed the full SM API Developer documentation (to the best of my ability) .

Instead of providing only hyperlinks to me, can you please provide more detailed instructions? I provided all my Postman screenshots previously to make it easier for you.

e.g. You might like to provide an example or correction of what the ‘POST’ API URL, Headers, Query Parameters, and/or Body code should read as. This would be helpful to me.

Thank You so much in-advance!

Kind regards,
Marc

5

Marc Fowler wrote:

Error 500 now

Hi Nicholas,

After your above response, I tried the following JSON etc…

Updated JSON payload you used:

{
“eventType”: 248556,
“scheduledAt”: “2025-07-21 14:00:00”,
“invitee”: {
“fullName”: “Marc Test”,
“email”: “test@example.com”
}
}

Updated headers used:

X-API-KEY: Ending in c8c
Content-Type: application/json
Accept: application/json
Confirm the endpoint URL:

POST https://secure.simplymeet.me/panel/api/event

Error 500:

I am now receiving a 500 Internal Server Error. The request body is validated correctly (no more 400 or 404), but the backend appears to crash while processing.

Can you confirm whether this is a bug or if my current structure is missing some undocumented requirement?

Kind regards,
Marc