Skip to main content

I'm accessing the REST API using a CURL command on Linux.

I tried Session Id and Authorization: Bearer as the connection method, but the result is the same.

 

The result is the following error:

 

[ {

"errorCode" : "NOT_FOUND",

"message" : "The requested resource does not exist"

} ]

 

I also use the --tls v1.2 option.

I'm working with the Bulk API the same way, but that's okay.

 

When executed in debug mode with the -v option.

 

* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 

* ALPN, server did not agree to a protocol 

* Server certificate: 

*  subject: C=US; ST=California; L=San Francisco; O=salesforce.com, inc.; CN=*.my.salesforce.com 

*  start date: Jul  9 00:00:00 2021 GMT 

*  expire date: Jul  8 23:59:59 2022 GMT 

*  subjectAltName: host "brave-hawk-3moqt3-dev-ed.my.salesforce.com" matched cert's "

*.my.salesforce.com

*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1 

*  SSL certificate verify ok.

 

This is a system administrator profile because it is running under my account. The API is set to be available.

Looking at the login history, there were no errors. 

 

I checked the following post, but couldn't solve it.

 

https://salesforce.stackexchange.com/questions/262796/rest-api-the-requested-resource-does-not-exist

 

https://help.crossbeam.com/en/articles/4136739-troubleshooting-your-salesforce-connection

12 respostas
  1. 7 de fev. de 2022, 08:39

    I'm not sure your access token is correct. An access token should look like:

    00D5e000001N20Q!ASAAQEDBeG8bOwPu8NWGsvFwWNfqHOp5ZcjMpFsU6yEMxTKdBuRXNzSZ8xGVyAiY8xoy1KYkaadzRlA2F5Zd3JXqLVitOdNS

     

    Notice the lack of \ after the org ID, as well as no underscores.

0/9000