Authentication
Configure authentication for your API connections
Authentication
Most APIs require authentication to access their data. API Mapper supports several authentication methods.
No Authentication
For public APIs that don't require authentication:
- Select None as the authentication type
- That's it - no additional configuration needed
Examples: JSONPlaceholder, REST Countries, some weather APIs
API Key
Many APIs use API keys for authentication. The key can be sent as a header or query parameter.
Header Authentication
Configuration:
- Select API Key as authentication type
- Set Location to Header
- Enter the Header Name (e.g.,
X-API-Key,Authorization) - Enter your API Key
Query Parameter
Configuration:
- Select API Key as authentication type
- Set Location to Query Parameter
- Enter the Parameter Name (e.g.,
api_key,key) - Enter your API Key
Bearer Token
OAuth2 and JWT-based APIs typically use Bearer tokens:
Configuration:
- Select Bearer Token as authentication type
- Enter your Token
For APIs with expiring tokens, you may need to periodically update the token in your connection settings.
Basic Authentication
Some APIs use HTTP Basic Auth with username and password:
Configuration:
- Select Basic Auth as authentication type
- Enter your Username
- Enter your Password
API Mapper automatically encodes the credentials.
Security Best Practices
Keep Credentials Secure
API keys and tokens are stored in your database. While they are not publicly visible, always:
- Use keys with minimal required permissions
- Rotate keys periodically
- Use read-only API access when possible
Troubleshooting Authentication
"401 Unauthorized" error
- Double-check your credentials
- Verify the authentication type matches what the API expects
- Check if the API key has expired
"403 Forbidden" error
- Your credentials may lack required permissions
- Some APIs restrict access by IP address
- Check API documentation for rate limits
Next Steps
Was this page helpful?