Does anyone have the super secret decoder ring for figuring out a salesforce client_id? I'm trying to connect to a sandbox with

<mailto:nate.atkins@company-domain--partibox.my.salesforce.com|nate.atkins@company-domain--partibox.my.salesforce.com>

I'm getting a

Response from Salesforce: {"error":"invalid_client_id","error_description":"client identifier invalid"}

did you discover how to handle this @Nathan Atkins?

Not yet. Not sure if I need something totally different than a username and password to get this to work.

@Anton Nosovitsky @Oliver Meyer @Marco Fontana (sorry to ping from nowhere) do you guys have any idea how to help Nathan? 😄

@Nathan Atkins Have you went through the guide linked?

It's like 3 step system to get a refresh toekn

https://medium.com/@bpmmendis94/obtain-access-refresh-tokens-from-salesforce-rest-api-a324fe4ccd9b and have this on

@Nathan Atkins have you figured it out? otherwise I can help with it (sorry, was off yesterday)

@Marco Fontana I'm getting back to this. I was on vacation last week. I'll let you know what I figure out.

I got it working with my personal developer SF. Thanks for the link.

@Marco Fontana Do you have an example of what the callback URL should be? We are getting the {"error":"redirect_uri_mismatch","error_description":"redirect_uri must match configuration"} error when we run the curl command to get the refresh token. We normally sign in through <company-name>.my.salesforce.com. We have set it to: https://<company-name>.lightning.force.com/api/connections/oauth/callback/ Does the name of the connected application need to go in there somewhere?

hey @Nathan Atkins weirdly I was getting a similar error using curl - installed postman and all worked properly

in my case the callback url is like

<https://mycompany-uat.my.salesforce.com/services/oauth2/token>...