Authentication

An API key is a unique identifier used to authenticate and authorize requests made to the API. It allows the system to recognize your account and verify that you have permission to access API services.

Your API key works like a password for your API access. It should be kept private and secure and should not be shared publicly or exposed in client-side code, public repositories, or with unauthorized users.

When making API requests, your API key is included with the request to confirm your identity and track your API usage, such as the number of requests made and available API credits.

If your API key is compromised, contact support or generate a new key to prevent unauthorized usage.

Create an account and register your email address. Once logged in, go to My Account → Settings → API Credits Settings. There you will find your API key, along with your remaining API credit balance.

Two equivalent styles are supported.

Option A — IYApiKey header (recommended in docs)

curl "https://data.importyeti.com/v1.0/company/ikea-supply" \
  -H "IYApiKey: YOUR_API_KEY"

Option B — Bearer token

You can also send the same API key as a standard Bearer token. Useful for clients that only support Authorization.

curl "https://data.importyeti.com/v1.0/company/ikea-supply" \
  -H "Authorization: Bearer YOUR_API_KEY"

When auth fails

Missing or invalid keys return HTTP 401:

{
  "message": "Unauthorized",
  "statusCode": 401
}

Key safety

• Store keys in environment variables or a secrets manager
• Never commit keys to git or paste them into public tickets
• The docs Try it console stores your key in browser localStorage only

MCP clients use the same API key (or an OAuth MCP token). See MCP.