> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundedperpetuals.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API Key Settings

> Create, copy, and revoke credentials for programmatic trading through the MyFundedPerps REST API.

<Warning>
  The developer API is in beta. Breaking changes may be introduced at any time.
</Warning>

[Open API Key settings](https://myfundedperpetuals.com/settings?section=api-keys)

## Create a key

Select **Create API Key** to open the creation dialog. It walks through four
steps:

1. Choose an environment, an access level, and an account boundary. The name
   is optional. If you leave it blank, MyFundedPerps uses a name in the
   format `Key generated on Month Day, Year`, using the UTC date.
2. Review the exact access granted to the key and confirm all three security
   and responsibility statements. Select **Back** to change the access.
3. Select **Continue** to send a six-digit verification code to your account
   email, then enter that code. The code expires after 10 minutes.
   Verification-code requests share the email limit used for sign-in: up to
   five codes per rolling minute and ten per rolling hour. If you reach either
   limit, the request control remains unavailable while an inline message
   counts down until you can request another code.
4. Select **Create API Key**.

The credential appears in a dialog after creation and is hidden by default.
Use **Show API Key** to reveal it or **Copy API Key** to copy it without
revealing it. MyFundedPerps stores only its cryptographic hash, so the
full key cannot be recovered or shown again after you close the dialog.

Choose **Read And Trade** only when the integration must create, modify, or
cancel orders. Account access can cover all accounts or one selected account.
You can hold up to five active keys per environment. Use separate names for
separate trading clients so you can revoke one integration without
interrupting another.

The **Environment** choice determines what the key can reach. **Live** keys
(`fp_live_`) serve requests on `developers.myfundedperpetuals.com` and reach
your challenge accounts. **Test (Sandbox)** keys (`fp_test_`) serve requests
on `sandbox.myfundedperpetuals.com` and reach only your sandbox accounts, free
paper accounts for testing an API integration. A sandbox account is created
for you automatically when you create a test key without an active one, and
every test key covers all of your sandbox accounts. Test-key creation
requires a challenge purchase in the last 90 days. See
[Sandbox and test keys](/sandbox) for the full workflow.

Keys created before access controls were available keep their existing read and
trading access to all accounts. Revoke and replace a legacy key to narrow it.

<Warning>
  Store API keys like passwords. Never commit one, print it in logs, include it
  in a URL, or embed it in browser or mobile application code. Anyone with the
  key can use its permissions without your password or another verification
  code. You are responsible for keeping the key secure. MyFundedPerps is not
  responsible for losses caused by a key you expose, share, or fail to secure.
</Warning>

## Revoke a key

Select **Revoke**, review the confirmation, then select **Revoke API Key**.
New requests using that key stop authenticating immediately. A request already
in flight may still finish.

For request examples, authentication rules, and endpoint schemas, read the
[developer API quickstart](/quickstart).