> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/api-keys-in-cortex-xsoar-8.md).

# API Keys in Cortex XSOAR 8

Cortex XSOAR 6 API keys are not migrated to Cortex XSOAR 8. You must create new API keys in Cortex XSOAR 8 SaaS/On-prem.

If using the migration wizard, for testing during the UAT phase and continued use on your Cortex XSOAR 8 tenant, you must create new API keys in Cortex XSOAR 8.

The following table describes the differences between Cortex XSOAR 6 and Cortex XSOAR 8:

| Cortex XSOAR 6                                                                                                                          | Cortex XSOAR 8                                                                                                                                                     |
| --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| API call header requires an API key.                                                                                                    | API call header requires an API key and API key ID.                                                                                                                |
| API keys are linked to a user and have the permissions of a specific user.                                                              | API keys are linked to a role and have the permissions of that role.                                                                                               |
| There is only one type of API key.                                                                                                      | There are two types of API keys: Standard and Advanced.                                                                                                            |
| API URLs consist of only the FQDN, the API name, and the name of the call. For example: `https://{fqdn}/{name of api}/{name of call}/`. | API URLs consist of an API prefix, the FQDN, XSOAR, the API name, and the name of the call. For example: `https://api-{fqdn}/xsoar/{name of api}/{name of call}/`. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/api-keys-in-cortex-xsoar-8.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.