# Registration & Authentication ### Registration Access to Vaultera PCI is only available by demand. Please, contact us via to get your account. We provide a free trial for any system. If you are a developer and wish to test please get in touch, the process is simple. We cannot provide self signup since it is a sensitive service. ### Authentication #### API Key Authentication After registration, you will receive `Master API Key`, which you can use as sign for your requests to our API. To sign request by API Key, you should pass it as a GET argument into your query: ``` GET https://pci.vaultera.co/api/v1/api_keys?api_key={YOUR_API_KEY} ``` {% hint style="warning" %} **MASTER API KEY NOTE** We strongly recommend that you don’t use the **Master API Key** for testing, development or production environments. Instead, you should generate a **Second API Key** (count is not limited) via our API Key methods and use that. If your **Second API Key** will be compromised, you can revoke it and generate a new one. {% endhint %} #### Session Token Authentication Embedded operations such as Show card iframe or Card capture iframe use a `Session Token` to handle authorization. `Session Token` is a one-off key to perform an operation at your account. We use a `Session Token` with embedded operations to prevent any potentials leaks, because the Embedded operations key is visible to the end client. Read more about Session Tokens here. --- # Agent Instructions: 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: ``` GET https://docs.vaultera.co/registration-and-authentication.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.