How to get a Capital.com API key for Autoview
Autoview turns a webhook from any system that can send one into an order on Capital.com. To do that, it needs three things from you: your Capital.com email, an API key, and the Custom Password you set for that key. This page shows where to get each one and which box it goes in on Autoview's Capital.com setup form.
The Capital.com steps below were checked against Capital.com's API documentation on October 6, 2026. If the platform looks different when you get there, Capital.com's page wins.
1. Start on Demo
Capital.com's API docs say a demo account can be used. Do that first. You get to watch real alerts turn into real orders with virtual money, and the setup is the same as live.
- Demo: connect on /account/setup/capital_demo/. It costs nothing on Autoview.
- Live: connect on /account/setup/capital/ once you're happy with how your alerts behave.
Both pages use the same form. The page you pick decides whether Autoview talks to Capital.com's demo server or its live one. The Capital.com Demo guide covers the demo account itself.
2. Create the key on Capital.com
You make the key inside Capital.com's platform, not inside Autoview.
- Turn on two-factor authentication (2FA). Capital.com requires it before it will issue a key. If 2FA is off, the platform asks you to switch it on. Capital.com's help center has steps for enabling 2FA.
- Open Settings, then API integrations. Log in on the web platform and find this section in Settings.
- Click Generate API key. A "Generate new key" window opens.
- Name the key. Something like "Autoview" makes it easy to spot later.
- Set the Custom Password. This is a new password just for this key. It is not your Capital.com login password. Pick one you don't use anywhere else, and write it down now.
- Choose an expiry date, or leave the default. Capital.com keys last one year by default. When a key expires, Capital.com deletes it and Autoview stops placing orders until you add a new one.
- Enter your 2FA code. Capital.com then shows the new API key.
- Copy the API key right away. Capital.com shows it only once. After that it appears as "****". If you lose it, you have to create a new key.
Keep the key and the Custom Password together somewhere safe. You need both on Autoview's form in a minute.
3. Permissions: nothing to pick
Many exchanges ask you to tick permission boxes, withdrawals among them. Capital.com doesn't. Its docs say there is only one kind of API key, and it allows trading. There is no read-only key and no permission list to set.
Autoview uses the key to read your accounts and positions and to manage orders on them. It has no withdrawal or transfer feature at all. The API key safety guide explains how Autoview stores keys.
You can switch a key off without deleting it. In Settings, API integrations, use the Pause icon next to the key, and Play to turn it back on. A paused key stops Autoview from trading until you resume it.
4. IP restriction
Capital.com's API documentation doesn't describe an IP allowlist for API keys, so there is no address to add. If you ever see an IP option on Capital.com's key page, follow Capital.com's own guidance for it. The addresses Autoview's servers trade from are listed in the API key safety guide, and support can confirm which one your account uses.
5. Which value goes in which field
Step 1 of Autoview's Capital.com setup form has three credential boxes, in this order:
| Autoview field | What to paste |
|---|---|
| *Email Address | The email you log in to Capital.com with. |
| *API Key | The key Capital.com showed you once, after the 2FA code. |
| *Custom Password | The password you set in the "Generate new key" window. Not your login password. |
Then pick a Zone and click Add API Keys. Steps 2 and 3 create a webhook and link it to the key. Step 4 runs a read-only test: it starts a session and lists the Capital.com accounts the key can reach. It places no orders. The Capital.com getting-started guide picks up from there with your first test order.
6. Common errors
- "Invalid API credentials." Capital.com refused the login. Most often the Custom Password field holds your login password instead of the key's password. Also check for a stray space in any field, and that the email matches the Capital.com account that owns the key.
- The test fails on the demo page but works on live, or the other way round. Make sure you're on the setup page for the account you mean to trade: Demo or Live.
- The key was working and then stopped. Check Settings, API integrations on Capital.com. The key may be paused, or it may have expired. Capital.com also deletes keys when an account is suspended or blocked.
- "Invalid Token provided", now and then. Capital.com ends an older session when a newer one starts with the same key. If another tool or script logs in with the key Autoview uses, they can knock each other out. Give Autoview its own key.
- I can't find the key or the Custom Password. Capital.com won't show either again. Create a new key, then update the connection on Autoview.
- The Generate API key button asks for 2FA. That's expected. Turn 2FA on first, then come back.
For order errors after you're connected, such as unknown symbols or a size below the minimum, see the Capital.com command reference.