Skip to main content
All API endpoints require authentication via an API key passed as a in the Authorization header. 
Authorization: Bearer tapi_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

​
Prerequisites

  • A TechnologyChecker account (sign up free)
  • Access to the Settings > Developers section in the dashboard

​
Key formats

TypePrefixUse case
Livetapi_live_Production requests that consume credits
Testtapi_test_Development and testing (limited functionality)

​
How to get your API key

1

Sign in

Go to app.technologychecker.io and sign in to your account.
2

Navigate to developers

Go to Settings > Developers.
3

Create your key

Click Create API key and copy the key — it is only shown once.
Each organization gets a single API key with encrypted storage. Usage is tracked via credits (limit, used, remaining) with a monthly reset date.
Keep your API key secret. Don’t expose it in client-side code, public repositories, or logs. If it’s compromised, revoke it immediately and generate a new one.

​
Example request

curl -H "Authorization: Bearer tapi_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  https://api.technologychecker.io/v1/domain/shopify.com
All /v1/* endpoints require authentication. Account endpoints like /v1/usage and /v1/credits do not consume credits.

Rate limits

Request limits by plan and retry strategies.

Credits

Credit costs per endpoint and plan details.

Errors

Error codes, response format, and retry logic.

API reference

Explore all endpoints with interactive examples.

​
Frequently asked questions

Don’t expose your API key in client-side code, public repositories, or logs. Store it in environment variables or a secrets manager. If your key gets compromised, revoke it immediately from Settings > Developers and generate a new one.
Each organization gets a single API key with encrypted storage. Usage is tracked via credits with a monthly reset date. All team members in your organization share the same key.
The API returns HTTP 401 with error code UNAUTHORIZED and the message “Missing or invalid API key.” Verify your Authorization header uses the format Bearer YOUR_API_KEY. See errors for all error codes.
Live keys (prefixed tapi_live_) make production requests that consume credits from your plan balance. Test keys (prefixed tapi_test_) are for development and testing with limited functionality — they won’t charge credits. Use test keys while building your integration, then switch to live keys when you’re ready for production.
No. API keys remain valid until you manually revoke them. There’s no automatic expiration or forced rotation schedule. If you suspect your key has been compromised, revoke it from Settings > Developers and create a new one immediately.
Go to Settings > Developers in your dashboard, revoke the current key, and create a new one. Update the key in all your applications before revoking — the old key stops working instantly. There’s no grace period.
No. TechnologyChecker only accepts API keys via the Authorization: Bearer YOUR_API_KEY header. Query parameter authentication isn’t supported because it exposes keys in server logs, browser history, and referrer headers. Header-based auth is the industry standard for REST APIs.