> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/security/api-keys.md).

# API Keys

StatusPal provides two types of API keys you can access to see and manage your status pages:

### User API key

Your user API key allows you to manage and/or read your status pages according to your user role within a StatusPal organization.

Access your user API key by clicking on <mark style="background-color:green;">My details</mark> from the top right profile icon:

<div align="left"><figure><img src="/files/WbPWX15Kbdpzy00u7GbZ" alt="StatuPal status pages API keys for users" width="375"><figcaption></figcaption></figure></div>

### Organization API keys

Organization API keys grant access to all the status pages within an organization, either read-only or read-and-write.

Manage your organization's API keys by visiting your organization's settings and clicking on <mark style="background-color:green;">Security > API Keys</mark>.

<div align="left"><figure><img src="/files/SDWi5kZYOG6xaIE9ATk7" alt="StatusPal status page API keys for organization" width="360"><figcaption></figcaption></figure></div>

### When to use which type of API key?

Organization API keys are preferred for integrations that act on an automated basis instead of on behalf of a specific person. It is important to select the minimum necessary access, and when possible, only read-only permissions should be granted.

A user-level API key can be used when an integration should act on behalf of a specific person. Furthermore, since organization API keys don't currently support restriction to specific status pages, user API keys can be used to give access to only a subset of the status pages in an organization.

{% hint style="info" %}
Have any thoughts about API keys? Drop us a line at [support@statuspal.io](support:support@statuspal.io).
{% endhint %}