Skip to main content

​
Environments

The API offers two environments: Sandbox and Production. The Sandbox environment is designed for testing and experimentation, allowing you to simulate API interactions without affecting real data. The Production environment handles live operations and requires verified credentials. Throughout this documentation, API endpoint references default to the Sandbox environment.

​
Sandbox

​
Production

​
Using and Managing Iron API Keys

To access the Iron API, you need to include a valid API key with each request. The API key acts as a unique identifier and ensures secure communication between your application and the API.

​
Managing API Keys in the Partner Dashboard

You can create and manage API keys in the Partner Dashboard.
1
Log in to the Partner Dashboard.
2
Navigate to Developer → API Keys.

​
Creating an API Key

When creating a new API key, you need to provide the following details:
  • Role: Define the key’s permissions:
    • Read Only: Read-only access.
    • Read / Write: Read and write access.
  • Label: A descriptive name to help you identify the key, especially if you manage multiple keys.

​
Revoking an API Key

You can revoke an API key at any time through the Partner Dashboard.

​
Using an API Key

Once you’ve created an API key, include it in the X-API-Key header of each request.

​
Example Request

Here’s an example using curl to fetch a list of customers: 
curl --request GET \
     --url https://api.sandbox.iron.xyz/api/customers \
     --header 'X-API-Key: YOUR-API-KEY' \
     --header 'accept: application/json; charset=utf-8'
Replace YOUR-API-KEY with the actual API key you generated. Ensure the X-API-Key header is included in every request to authenticate your access.

​
MCP Server

📦 https://www.npmjs.com/package/@ironxyz/mcp-server Some examples of what you can do with it:
  1. Cursor automatically locates the Iron.xyz MCP server.
  2. It retrieves a summary list of all available endpoints and identifies the correct one to use.
  3. It fetches the complete OpenAPI specification for the selected endpoint.
  4. It implements a full Golang backend based on that spec.
  5. It makes a real API call to the sandbox endpoint and returns the live response within the Cursor chat.