Here is an example response object:
Open in a new tab here: /api-reference/minting/nfts/mint-nft
Crossmint has a 10MB re-upload size limit. For larger files, upload your media to IPFS, create a metadata.json as shown above, submit the metadata file's URL, and ensure `reuploadLinkedFiles` is set to `false`.
The default option is `true`.
Here is an example response object:
# Overview
Source: https://docs.crossmint.com/authentication/introduction
A user management solution tightly integrated with all other Crossmint products
Authenticate users using web3 or traditional sign-in methods:
* **Email OTP**: passwordless sign-in using a one time code delivered to the user's email.
* **Social Accounts**: Sign in with Google, Apple, X, and more.
* **Farcaster**: using the [Sign In With Farcaster (SIWF) standard](https://github.com/farcasterxyz/protocol/discussions/110).
* **External wallets**: connect with crypto wallets for Web3 authentication.
## Key Characteristics
```
✅ Login successful! You are now authenticated in the Production environment.
```
You'll then be prompted to select a project:
```
? Select a project: (Use arrow keys)
> My Project
Website Integration
Mobile App
```
# Crossmint logout
Source: https://docs.crossmint.com/cli/logout
Sign out from the Crossmint platform
The logout command signs you out from the Crossmint platform by removing your session token from local storage.
To use it, run the following command from your terminal
```bash theme={null}
crossmint logout
```
## Example
Sign out from Crossmint:
```bash theme={null}
crossmint logout
```
After running the command, you'll see a confirmation message:
```
✅ Logout successful! You are no longer authenticated.
```
After logging out, you will need to use the `login` command to authenticate again before using other commands that require authentication.
# Crossmint projects create
Source: https://docs.crossmint.com/cli/projects/create
Create a new project in Crossmint
The projects create command allows you to create a new project in your Crossmint account.
To use it, run the following command from your terminal
```bash theme={null}
crossmint projects create [options]
```
## Options
| Option | Description |
| ------------------- | ------------------------ |
| `-n, --name 
### Setting Authorized Origins
Client-side keys are exposed in the application and thus require additional security measures. The minimum requirement is to whitelist URLs that requests can be sent from. Client-side keys support two types of origins:
### Select Scopes
Within the modal that opens, toggle the required scopes you want to enable. You may need to expand an accordion for the product area you're working on to expose additional scope options.
For more information on API Key scopes visit the scopes page or the API Reference.
## Third Party Authentication
For projects that have already implemented authentication using one of the supported providers, you can provide Crossmint with the appropriate project/environment/app ID from the settings page of the third party. Supported providers include: Dynamic, Auth0, Stytch, Privy, Firebase, Kinde, and Supabase.
To use this option, select the 3P Auth providers option, then choose your provider from the dropdown. Next, you'll need to find the appropriate ID that your provider gives you to identify your project. This can typically be found within the settings pane of their web interface.
## Custom JWT Auth
If your project is using an auth provider not listed in the 3P providers list or is a home-grown JWT solution, you can choose the Custom tokens option. You will need to be able to provide a 
For a detailed guide on implementing this approach, check out the [Custom JWT Authentication Guide](/introduction/platform/api-keys/custom-jwt-auth-guide).
# Overview
Source: https://docs.crossmint.com/introduction/platform/api-keys/overview
Get your keys in seconds and start building
API keys are required to authorize requests against the Crossmint APIs. By using an API key, Crossmint knows which project is making the call, and can deduct credits from your balance.
## Staging vs. Production Keys
First, determine if you need a staging (testing) or production API key.
### Select Scopes
You can determine the scopes you need by visiting the API reference page for the API(s) you need to interact with.
## Privacy Policy
Projects have an option to register a link to your company's privacy policy. If set, this link will be shown to your users when they're using any Crossmint-managed user interface, such as the Checkout, where user information is collected. A privacy policy is required by law if you want to later those users' personally identifiable information, such as their email address.
If you don't already have a privacy policy, you can generate and host one using tools like [Termly](https://termly.io/).
> **Note:** Failure to add a privacy policy will result in email addresses being hidden.
#### Cases Requiring a Privacy Policy to Access User Data
| Use Case | Privacy Policy Required |
| ---------------------------- | ----------------------- |
| Payments (payment button) | Yes |
| Payments (embedded checkout) | Yes |
| Payments (headless checkout) | No |
| Mint API or console | No |
| Wallet APIs or console | No |
### Steps to Add a Privacy Policy Link
1. \**Go to the General Settings tab*
* Access the Settings page from the sidear.
2. **Include the Privacy Policy Link**
* In the project settings, locate the section for adding a privacy policy.
* Paste the URL of your privacy policy generated from Termly or any other source.
4. **Verify Email Visibility**
* After adding the privacy policy link, check to ensure that email addresses are now visible.
* If the link is not included, emails will remain hidden to protect user data.
Following these steps will ensure compliance with data protection laws and enable the visibility of email addresses in your project settings.
***
## FAQs
### FAQs
### Step 2: Prepare Your Metadata
Before uploading your assets, you need to prepare them properly:
1. You can upload up to 1,000 NFT collectibles at once
2. Download the example CSV file provided by Crossmint to use as a template
3. Prepare your metadata according to the template format
### Step 3: Upload Your Metadata CSV
1. Add a CSV file named `metadata.csv` with your NFT metadata
2. Click the "Upload CSV" button to upload your prepared file
### Step 4: Upload Media Files
1. Prepare your NFT media files (images, animations, videos)
2. Crossmint supports various formats (PNG, JPEG, GIF etc.)
3. Each file must be under 10MB in size
4. All media files should be in the same folder, not in subfolders
5. Click "Upload media files" to upload your prepared media
### Step 5: Complete the Upload
After uploading both your metadata CSV and media files, click the "Upload" button to start the batch minting process.
## Monitoring Bulk Operations
When minting in bulk, it's essential to track the status of your operations:
1. **Webhooks**: Set up [webhooks](/minting/nfts/integrate/webhooks-and-status-apis) to receive real-time notifications about mint completions and failures
2. **Status API**: Use the [action status API](/minting/nfts/integrate/webhooks-and-status-apis) to check the status of individual minting operations
3. **Console Dashboard**: Monitor your minting operations through the Crossmint Console
# Mint Tokens
Source: https://docs.crossmint.com/minting/nfts/integrate/mint-tokens
Create and distribute tokens at scale
## Integration steps
## Using Template IDs
See the embedded checkout in action on the [Crossmint Playground](https://playground.crossmint.com/checkout/embedded).
## When is the Embedded Checkout the best fit?
* **You want to insert the checkout into your site**
* **You want high level of control over the UI/UX**
## Get Started
Note the quote expiration timer above the checkout button.
🎉 Congratulations! You've successfully set up your embedded memecoin checkout. Check out the [Next Steps](#next-steps) section below to learn how to customize your integration.
# Pay with Card - NFTs
Source: https://docs.crossmint.com/payments/embedded/quickstarts/credit-card-nft
Embed a onchain checkout into a web app in under 5 minutes
### Fee Sponsorship
This option enables you to control who pays the fees of the NFT purchase including gas and credit card transaction fees. The default option is "Buyer", which means that if you set a price of 10 USDC, the final price the buyer pays will be 10 USDC plus fees.
If you want to provide a consistent price for your customers, select the "You" option to sponsor the fees. When you sponsor the fees they will be deducted from the amount the buyer pays and the remainder will be paid to the recipient wallet you set in the next step.
#### Recipient Address
Enter the wallet address where you want to receive payments. This is the address where Crossmint will send the proceeds from NFT sales.
Click the `Create NFT` button to complete.
There is one additional step when using a client-side API key in your application with headless checkout. The first call will be to create the order. The response will include a `clientSecret` property that you must persist in state and then pass as an additional header in subsequent API requests to the [update-order](/api-reference/headless/edit-order) or [get-order](/api-reference/headless/get-order) routes.
### Client Side Example Code
3. Click the "Integrate" tab and select the "API Keys" section on top
Before creating an API key, you'll need to decide on server-side vs client-side implementation. You can find some more info in the [Client or Server Guide](/payments/headless/guides/client-or-server).
## Next Steps
You're ready to move on to implementing the Headless Checkout in your application!
# Production Launch
Source: https://docs.crossmint.com/payments/headless/guides/production-launch
Follow this checklist to ensure you are ready for production launch with Headless Checkout
## From Staging to Production with Headless Checkout
