---
schema_version: "1"
id: 7ea14a1d937d9cdce9181ec4e382a7fdc71b19a48ad3b2185193ec05a0503855
title: Accessing Own through the Own API
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/platform_o_access_through_api.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.platform_o_access_through_api.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 34b3fee176d228e0a7ab7948a00d3e326252375415ad810fa15f13aa004afc27
description: Own provides API access through all pricing plans with the purpose of letting you manipulate and export some of your jobs and data.
products:
  - Security
  - Salesforce Platform
release: "264"
---
# Accessing Own through the Own API

Own provides API access through all pricing plans with the purpose of letting you manipulate and export some of your jobs and data.

See [Own API](https://developer.salesforce.com/docs/platform/own-api/references/own-api-rest) for guidelines to the API guide along with sample requests and responses for:

- Service
- Backup
- Objects
- Job
- GDPR
- Event
- Sandbox Seeding

Common use cases of API access include:

- GDPR request relay from Salesforce: automating the General Data Protection Regulation process end to end from Salesforce to include snapshots as well.
- Audit log monitoring: Integrate the events audit log to your central monitoring system for important or suspicious behavior.
- Export backup to SQL: Automate backups to a 3rd party database for further processing (such as BI or BA).
- Execute Sandbox Seeding jobs: Kickoff jobs directly from the API.

## Managing an API Token for your Account

Use of API Tokens, based on OAuth 2.0 authentication protocol, as a means to access Own from Salesforce APIs. Your API token needs to be treated as securely as any other type of password. Make sure to store this token in a safe and secure location.

## Using API Token

Update your API scripts with our new domain.

Tokens will automatically expire and be deleted after 180 days (regardless if the token was in use or not). Once expired and deleted, the token will not be available to the user, and the user account will not have access to our APIs. Therefore, API tokens must be revoked and regenerated, before they expire.

Only one API token can exist, for any user, at any one time.

After generating a new API token, insert the new access key generated, into the script in the API. See the API documentation.

API Tokens are cross-regional (one API Token for all regions). The user’s access is determined by his role and the Business Units he belongs to.

If you need to disable the API Token option (to limit access by users), contact support.

- **[Manage API Tokens](https://help.salesforce.com/s/articleView?id=platform.platform_o_manage_api_tokens.htm&release=264.0.0&type=5)**  
    Use API Tokens, based on OAuth 2.0 authentication protocol, as a means to access Own from Salesforce APIs. Treat API tokens as securely as any other type of password. Make sure to store this token in a safe and secure location.
- **[Securing Your API Token](https://help.salesforce.com/s/articleView?id=platform.platform_o_secure_api_token.htm&release=264.0.0&type=5)**  
    An API token is a refresh token that is used to generate an authentication token in order to sign in to the Own Data Platform via API, in order to perform various operations within the Own account.