# Accounts

Sub-Account (Formerly Location) Documentation for Sub-Account (Formerly location) API Before you can create or publish a Marketplace app, you need access to the Marketplace Developer Portal.

## Pages in this folder

| Page | Local file | Summary |
| --- | --- | --- |
| Sub-Account (Formerly Location) | [sub-account-formerly-location.md](sub-account-formerly-location.md) | Sub-Account (Formerly Location) |
| Sub-Account (Formerly location) API | [sub-account-formerly-location-api.md](sub-account-formerly-location-api.md) | Documentation for Sub-Account (Formerly location) API |
| Step 1: Create a Developer Account | [step-1-create-a-developer-account.md](step-1-create-a-developer-account.md) | Before you can create or publish a Marketplace app, you need access to the Marketplace Developer Portal. This is where you manage your apps, team access, OAuth settings, and submission workflow. |
| Set Accounts | [set-accounts.md](set-accounts.md) | Set social media accounts for a CSV import to publish posts to |
| Sandbox Account – Fair Use Policy | [sandbox-account-fair-use-policy.md](sandbox-account-fair-use-policy.md) | Purpose |
| Put Sub-Account (Formerly Location) | [put-sub-account-formerly-location.md](put-sub-account-formerly-location.md) | Update a Sub-Account (Formerly Location) based on the data provided |
| Private Integration Tokens (PIT) for Sandbox Accounts | [private-integration-tokens-pit-for-sandbox-accounts.md](private-integration-tokens-pit-for-sandbox-accounts.md) | A **Private Integration Token (PIT)** is a **scoped authentication token** that provides **secure server-to-server** access to **HighLevel APIs**. |
| Multi-Account Support & User Info | [multi-account-support-user-info.md](multi-account-support-user-info.md) | This section covers two related capabilities that work for both OAuth 2.0 and API Key / Basic Auth: |
| Handling Access Tokens for Apps with Target User: Sub-Account | [handling-access-tokens-for-apps-with-target-user-sub-account.md](handling-access-tokens-for-apps-with-target-user-sub-account.md) | This document explains how to manage Access Tokens when your app’s Target User is set to Sub-Account. |
| GHL Marketplace Sandbox Accounts: Setup and Usage Guide | [ghl-marketplace-sandbox-accounts-setup-and-usage-guide.md](ghl-marketplace-sandbox-accounts-setup-and-usage-guide.md) | A Sandbox account is a non-production HighLevel environment created for Marketplace developers. |
| Get Sub-Account (Formerly Location) | [get-sub-account-formerly-location.md](get-sub-account-formerly-location.md) | Get details of a Sub-Account (Formerly Location) by passing the sub-account id |
| Get Instagram accounts for page | [get-instagram-accounts-for-page.md](get-instagram-accounts-for-page.md) | Retrieve Instagram accounts linked to a specific Facebook page |
| Get Google ad accounts | [get-google-ad-accounts.md](get-google-ad-accounts.md) | Retrieve Google Ads accounts available for the connected user |
| Get Available Accounts (Step 2 of 3) | [get-available-accounts-step-2-of-3.md](get-available-accounts-step-2-of-3.md) | ## OAuth Connection Flow - Step 2: Get Available Accounts |
| Get all associations for a sub-account / location | [get-all-associations-for-a-sub-account-location.md](get-all-associations-for-a-sub-account-location.md) | Get all Associations |
| Get ad accounts | [get-ad-accounts.md](get-ad-accounts.md) | Retrieve Facebook ad accounts available for the connected user |
| Get ad account details | [google-get-ad-account-details.md](google-get-ad-account-details.md) | Retrieve details of a specific Google Ads account |
| Get ad account details | [fb-get-ad-account.md](fb-get-ad-account.md) | Retrieve details of a specific Facebook ad account |
| Get ad account details | [li-get-ad-account-details.md](li-get-ad-account-details.md) | Retrieve details of a specific LinkedIn ad account |
| Get Accounts | [get-accounts.md](get-accounts.md) | Get list of accounts and groups |
| Enable SaaS for Sub-Account (Formerly Location) | [enable-saas-for-sub-account-formerly-location.md](enable-saas-for-sub-account-formerly-location.md) | Enable SaaS for Sub-Account (Formerly Location) |
| Delete Sub-Account (Formerly Location) | [delete-sub-account-formerly-location.md](delete-sub-account-formerly-location.md) | Delete a Sub-Account (Formerly Location) from the Agency |
| Delete ad account | [google-delete-ad-account.md](google-delete-ad-account.md) | Remove a Google Ads account connection from a location |
| Delete ad account | [fb-delete-ad-account.md](fb-delete-ad-account.md) | Remove a Facebook ad account connection from a location |
| Delete ad account | [li-delete-ad-account.md](li-delete-ad-account.md) | Remove a LinkedIn ad account connection from a location |
| Delete Account | [delete-account.md](delete-account.md) | Delete account and account from group |
| Create Sub-Account (Formerly Location) | [create-sub-account-formerly-location.md](create-sub-account-formerly-location.md) | Create Sub-Account (Formerly Location) https://services.leadconnectorhq.com/locations/ Create a new Sub-Account (Formerly Location) based on the data provided This feature is only available on Agency Pro ($497) plan. |
| Connect Account (Step 3 of 3) | [connect-account-step-3-of-3.md](connect-account-step-3-of-3.md) | ## OAuth Connection Flow - Step 3: Connect the Account |
| Check if account has sufficient funds | [check-if-account-has-sufficient-funds.md](check-if-account-has-sufficient-funds.md) | Check if account has sufficient funds |
| Account | [account.md](account.md) | Account |
| Access Token Generation: Agency vs. Sub-Account Scenarios | [access-token-generation-agency-vs-sub-account-scenarios.md](access-token-generation-agency-vs-sub-account-scenarios.md) | The type of Access Token that is generated depends on who is installing the app (an agency or a sub-account) and the app's distribution settings. Understanding these scenarios is crucial for developers to ensure their app correctly authenticates and functions as expected. Below, we'll outline the different contexts that determine whether an Agency-level or Sub-Account (Location-level) Access Token is issued. |
| Handling Access Tokens for Apps with Target User: Sub-Account - HighLevel API | [handling-access-tokens-for-apps-with-target-user-sub-account-highlevel-api.md](handling-access-tokens-for-apps-with-target-user-sub-account-highlevel-api.md) | This document explains how to manage Access Tokens when your app’s Target User is set to Sub-Account. |
| Get LinkedIn ad accounts | [li-get-ad-accounts.md](li-get-ad-accounts.md) | Get LinkedIn ad accounts |