Up next in 10
Blog Post:
https://www.infallibletechie.com/2026/07/salesforce-apis-license-and-terms-of-service.html
Show More Show Less View Video Transcript
0:07
Hello everyone. In this video, we are
0:10
going to see Salesforce new
0:13
license and terms of services for their
0:16
APIs.
0:18
If you received an email regarding new
0:21
changes for Salesforce APIs,
0:24
and
0:25
if you wanted to have a quick summary
0:27
and quickly understand the changes that
0:30
are coming, then you can make use of
0:32
this video as a reference.
0:36
The first
0:38
uh thing what we have to
0:40
um
0:41
learn about the new terms and
0:44
uh services is
0:46
authority and binding agreement.
0:49
As an individual user and as the
0:52
organization or as an entity, you have
0:55
to
0:56
accept
0:58
the new terms and services.
1:00
If you check the email,
1:04
starting 60 days of this email,
1:07
you will be prompted to review and
1:09
accept the new Salesforce APIs license
1:11
and terms of use.
1:14
The next thing is
1:16
permitted use and license.
1:19
The Salesforce APIs
1:22
are not trans- transferable
1:25
and it is
1:27
limited license to access Salesforce
1:29
APIs to build, integrate, or maintain
1:31
applications that interoperate with
1:34
Salesforce services only.
1:37
The scope of this uh
1:39
the uh the scope of Salesforce APIs is
1:43
it is restricted to internal business
1:45
purposes or designated application
1:48
functionality approved under the
1:50
developer agreements.
1:54
The next thing is restrictions and
1:56
prohibited uses. We cannot resell
2:00
the Salesforce APIs.
2:02
So, if you are
2:04
using Salesforce APIs
2:06
and you cannot charge on on the usage of
2:10
Salesforce APIs from other entities. So,
2:13
there is no reselling or or
2:15
redistribution.
2:16
And we cannot do competitive
2:19
benchmarking.
2:20
Do not try to compare
2:24
Salesforce APIs with a different APIs
2:26
and you cannot monitor the performance,
2:29
availability, and you cannot do any
2:31
competitive analysis or benchmarking
2:34
without any written authorization. So,
2:36
make sure you are
2:37
if you wanted to do this, then make sure
2:40
you are getting written authorization
2:42
from Salesforce.
2:43
Next is
2:45
we should not do any reverse engineering
2:47
or modification to the Salesforce APIs.
2:55
Make sure
2:56
the APIs uses only acceptable content.
3:02
The APIs must not be used to store,
3:04
process, or transmit libelous,
3:07
infringing, unlawful, unlawful, or
3:10
harmful material
3:12
or any data or any information that
3:15
violate privacy rights. So, before
3:17
invoking Salesforce APIs, it is our
3:20
responsibility to make sure we are not
3:24
using any bad data to the Salesforce
3:28
APIs. So, make sure we are following
3:30
that.
3:31
The next thing is data protection and
3:34
complaints.
3:35
It is customer responsibility.
3:38
That is the users are solely responsible
3:40
for the accuracy, quality, and legality
3:42
of the data transmitted via the API. It
3:45
is same as that.
3:47
Acceptable content.
3:49
Policy
3:50
adherence.
3:52
We all know that Salesforce have
3:54
policies for using the
3:58
uh APIs. If it is for external facing
4:00
services policy, we have external facing
4:03
policy services. And Salesforce APIs
4:06
also have data privacy guidelines. So,
4:08
make sure all these guidelines and
4:11
services policy are maintained when you
4:15
are using Salesforce APIs.
4:18
Next, the warranties and liabilities and
4:20
disclaimers.
4:21
Salesforce is not responsible. It
4:24
disclaims that liability for direct,
4:26
indirect, incidental, consequential, or
4:29
punitive damages, as well as lost
4:32
profits or lost data resulting from any
4:35
Salesforce API usages. So, make sure
4:38
that we are aware of this.
4:41
Next, and uh the final thing is
4:43
Salesforce have full rights to modify
4:47
these API terms.
4:49
And uh they have rights to update the
4:52
technical documentation, limitation.
4:55
If they wanted to update the endpoints,
4:57
they can do it.
4:58
And uh
5:00
they can do it
5:01
um
5:02
before
5:04
or uh
5:05
or giving any prior notice also. They
5:07
have full rights to update the
5:09
Salesforce
5:10
APIs endpoints, terms, and
5:13
documentation, and usage.
5:15
If you want to keep yourself updated,
5:18
please make use of the Salesforce
5:20
article. I have given this in the last
5:23
reference section. Always keep checking
5:25
this. If you are a Salesforce admin,
5:27
developer, or an architect, or a
5:29
consultant who is working on Salesforce
5:31
integration,
5:33
please make sure you are following all
5:35
these uh
5:37
uh
5:37
new Salesforce APIs license and terms of
5:40
service
5:41
whenever you do any integration with
5:44
your third-party application. So, before
5:46
using any Salesforce APIs, if you have
5:49
to make sure we adhere to the new
5:52
Salesforce APIs license and terms of
5:55
service.
6:03
I hope it was helpful.
6:12
Thank you for watching.
#Internet Software
#Science