-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error message not in response.message #29
Comments
@jharbert Yes, I see something like that, too. And I'm oddly getting that exact same error on a call to cancel a class. This is an example failure response I've gotten when calling
I have no idea why I see that message when I cancel a class -- seems weird. But anyway, yes, I have to dig down into |
Is MindBody returning that message at the top level of the response? |
@wingrunr21 here is the XML response. There was a generic message in the top-level <?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<RemoveClientsFromClassesResponse xmlns="http://clients.mindbodyonline.com/api/0_5">
<RemoveClientsFromClassesResult>
<Status>FailedAction</Status>
<ErrorCode>200</ErrorCode>
<Message>An action has failed. Please see object message for details.</Message>
<XMLDetail>Full</XMLDetail>
<ResultCount>0</ResultCount>
<CurrentPageIndex>0</CurrentPageIndex>
<TotalPageCount>0</TotalPageCount>
<Classes>
<Class>
<ClassScheduleID>285</ClassScheduleID>
<Clients>
<Client>
<Messages>
<string>100003091 Already booked ClassID: 14910 - Client is already booked at this time</string>
</Messages>
<Username>XXXXXXXXXXXXXXXX</Username>
<MobileProvider xsi:nil="true" />
<AppointmentGenderPreference>None</AppointmentGenderPreference>
<IsCompany>false</IsCompany>
<LiabilityRelease>false</LiabilityRelease>
<PromotionalEmailOptIn>true</PromotionalEmailOptIn>
<CreationDate>2016-01-31T20:15:05.98</CreationDate>
<Liability>
<IsReleased>false</IsReleased>
<AgreementDate xsi:nil="true" />
<ReleasedBy xsi:nil="true" />
</Liability>
<Action>Failed</Action>
<ID>100003091</ID>
<FirstName>XXXX</FirstName>
<LastName>XXXX</LastName>
<Email>XXXX</Email>
<EmailOptIn>false</EmailOptIn>
<AddressLine1>XXXX</AddressLine1>
<City>Dallas</City>
<State>TX</State>
<PostalCode>75230</PostalCode>
<Country>US</Country>
<MobilePhone>XXXX</MobilePhone>
<HomePhone>XXXX</HomePhone>
<BirthDate>XXXX</BirthDate>
<FirstAppointmentDate xsi:nil="true" />
<ReferredBy>XXXX</ReferredBy>
<IsProspect>false</IsProspect>
<ContactMethod>1</ContactMethod>
</Client>
</Clients>
<Location>
...
</Location>
<MaxCapacity xsi:nil="true" />
<WebCapacity xsi:nil="true" />
<TotalBooked xsi:nil="true" />
<TotalBookedWaitlist xsi:nil="true" />
<WebBooked xsi:nil="true" />
<SemesterID xsi:nil="true" />
<IsCanceled>false</IsCanceled>
<Substitute>false</Substitute>
<Active>true</Active>
<IsWaitlistAvailable>false</IsWaitlistAvailable>
<IsEnrolled>false</IsEnrolled>
<HideCancel>false</HideCancel>
<ID>14910</ID>
<IsAvailable>true</IsAvailable>
<StartDateTime>2016-03-12T18:30:00</StartDateTime>
<EndDateTime>2016-03-12T21:30:00</EndDateTime>
<ClassDescription>
...
</ClassDescription>
<Staff>
...
</Staff>
</Class>
</Classes>
</RemoveClientsFromClassesResult>
</RemoveClientsFromClassesResponse>
</soap:Body>
</soap:Envelope> |
It seems like, in my case, you're doing the right thing by passing me the top level message. If I have a complaint, it'd be directed toward MindBody burying their error message. |
Yes, that is MindBody being helpful as usual. I'd follow up with MindBody (although FYI they are not very receptive to API feedback. I've been fighting for timezones in their timestamps forever now). So as this is not a code issue, would there be a preferable API? |
Wondering if you have thoughts on this.
If a client is already booked at some time, and you attempt to create another appointment with them at the time in which they are already booked, the request fails but there is no message in the response:
However there is an error in the response body:
Here's the full response:
The text was updated successfully, but these errors were encountered: