# Enigma Vault API

> Enigma Vault is a REST API that encrypts and tokenizes sensitive data. Card Vault stores and tokenizes payment cards and forwards them to payment gateways through a proxy. Data Vault encrypts and tokenizes searchable fields. File Vault stores encrypted files up to 5 GB. Customer Vault collects files, cards and signatures through intake links.

The API is versioned (1.0 to 1.14). Use the newest version, 1.14, unless an integration is pinned to an older one. Requests go to https://api.enigmavault.io and are authorized with an OAuth 2.0 client-credentials bearer token; the version is chosen with the `x-api-version` header.

## API reference

- [OpenAPI 3 spec, version 1.14 (JSON)](https://docs.enigmavault.io/1.14/swagger.json): The machine-readable definition of every endpoint, parameter, schema and scope. Start here.
- [API reference, version 1.14 (HTML)](https://docs.enigmavault.io/1.14/redoc-static.html): The same reference as a single readable page, with authentication and version notes.
- [All API versions](https://docs.enigmavault.io/): Index of the reference for versions 1.0 to 1.14. Each version's spec is at `/{version}/swagger.json`.

## Guides and examples

- [Card Vault integration examples](https://github.com/Enigma-Vault/card-vault-integration-examples): Working sample code for the hosted card form and the gateway proxy.
- [Pricing and plan limits](https://docs.enigmavault.io/pricing.html): Plans, included requests and overage.
- [Product documentation](https://www.enigmavault.io/docs/): Overview of the Vault API and NoPII setup guides.

## Optional

- [Swagger UI](https://api.enigmavault.io): Try requests live against the API.
- [Status page](https://enigmavault.statuspage.io/): Current availability.