REST ContactSvc

Has anyone been able to use REST to communicate with the Contact Service? We would like to use api/v1/Erp.BO.ContactSvc/Contacts to pass in the company and customer number(or customer ID) to get customer contacts but all attempts result in error 500. We are only able to get the Erp.BO.ContactSvc/List to work.

Thanks,
Tanner

Are you trying to do a read only query? If so I ALWAYS ALWAYS Recommend using a BAQ. it is faster and much more less expensive than any of the other API’s.

1 Like

Thanks for the advice! In this case, we are doing read only so we could make that work. However, the guy I have working on the web pages does not have BAQ writing skills and it would be simpler if the interfaces worked as documented in swagger.

that ContactsSvc is not a usual server - it does not have all standard methods implemented, that is why you have 500 error.
You can use existing custom methods though they are not OData.

1 Like

Thanks for the quick response! Is there a plan to implement those services or a place to see which services are fully implemented? If not, is there any plan to hide the interfaces to minimize confusion for newbies?

we have story for REST to hide such not-working service methods, but I cannot say when it will be implemented. REST only uses what exists in the backend.

As always, features with customer tickets attached to them get higher emphasis. Submitting a request helps me to push ‘x’ over ‘y’ :slight_smile:

Thanks, I will definitely keep that in mind as we encounter other issues with REST. It has been my experience that this forum is much more receptive/accessible than Epicor support. Thank the IT gods for this site!

Hey all, what is the current status of the ContactSvc? It’s been almost 2 years since the solution to this was posted. For me, the ContactSvc is still documented in swagger, and still returns a 500 response code : “Sorry! Something went wrong. Please contact your system administrator”.

Use CustCntSvc instead