# API App
> Click here to learn how to manage your Dropbox Sign App using the API.
# API App
API Apps are most commonly used by developers building with [embedded workflows](/api/reference/embedded) or [OAuth](/docs/oauth/overview). When an API App is created, a unique `client_id` is assigned to that API App, which is used in both the server and client side requests that make up embedded workflows.
A single account can own multiple API Apps, and they can be created and managed programmatically through the API App endpoints or through the web on Dropbox Sign's [API settings](https://app.hellosign.com/home/myAccount#api) page. Using multiple API apps is a great approach to managing custom branding on a per-signature request basis.
* Configure an app's custom branding by calling [Update API App](/api/reference/operation/apiAppUpdate/)
* Change the `client_id` between calls to apply that branding on that respective app
The API App object contains an `owner_account` [object](/api/reference/operation/apiAppList/#!c=200\&path=api_apps/owner_account\&t=response) that team admins can use for visibility into which accounts on the team have created API apps.
## API App Endpoints
| Summary | Endpoint | Description |
| -------------------------------------------------------- | ------------------------------------- | ------------------------------------------------------ |
| [GET API App](/api/reference/operation/apiAppGet/) | /api\_app/\{client\_id} | Returns an object with information about an API App. |
| [List API Apps](/api/reference/operation/apiAppList/) | /api\_app/list | Returns a list of API Apps that are accessible by you. |
| [Create API App](/api/reference/operation/apiAppCreate/) | /api\_app | Creates a new API App. |
| [Update API App](/api/reference/operation/apiAppUpdate/) | PUT
/api\_app/\{client\_id} | Updates an existing API App. |
| [Delete API App](/api/reference/operation/apiAppDelete/) | DELETE
/api\_app/\{client\_id} | Deletes an API App. |