Not enough information here, please provide traces of the JSON you're sending and receiving and the exact URLs you're trying to access. You will want to redact the client_id, client_secret, and access_token of course, but please keep your report readable. Use the Advanced Editor's syntax highlighter to highlight the JSON (choose JavaScript from the language dropdown).
Sanford,
Here is the additional information you requested. Thank you in advance for following up on this.
POST https://204-poc-794.mktorest.com/rest/v1/leads.json?access_token=85a52596-82e4-41e5-9a32-ed9960ec6a5... HTTP/1.1
Host: 204-poc-794.mktorest.com
Accept: application/json
Connection: Keep-Alive
Request-Id: |cf9b0e30-4003b18fddb65ac0.2.
Content-Type: application/json
Content-Length: 198
{"lookupField":"email","input":[{"firstName":"Maleine","lastName":"MCCONNON","dateOfBirth":"1968-10-16T00:00:00","mainPhone":"9182911721","postalCode":"74115","email":"Maleine.MCCONNON@slc02.com"}]}
Response Received
HTTP/1.1 200 OK
Server: nginx
Date: Mon, 04 Nov 2019 19:10:06 GMT
Content-Type: application/json;charset=UTF-8
Content-Length: 101
Connection: keep-alive
{"requestId":"12fc9#16e37d304bd","success":false,"errors":[{"code":"603","message":"Access denied"}]}
Can you show the LaunchPoint service setup and API-only user/role associated with this call? This still looks like a role permissions issue to me.
I have the same problem, did you find a solution for this matter?
in my case the error was related with the token parameters I wanted to pull users but instead of sending the token using query parameters it has to be using header, I hope this helps