Authentication
All Redpin APIs require authentication to secure your data and ensure proper access control.
Our APIs support two authentication methods depending on the context:
API Key Authentication
How to Use API Keys
Include your API key in the apikey header with every request:
For example:
Never expose your API key in client-side code. Always make API calls from your server.
Obtaining an API Key
API keys are provided to approved partners. To request an API key:
- Contact our Partner Integrations Team
- Receive your unique API key for integration
OAuth 2.0 Authentication
OAuth 2.0 Client Credentials Flow
The Client Credentials flow is designed for server-to-server authentication:
- Your application requests an access token using your client credentials
- Our authorization server validates your credentials and issues an access token
- Your application uses the access token to authenticate API requests
Requesting an Access Token
Make a POST request to our token endpoint:
The response will include an access token and expiration time:
Using the Access Token
Include the access token in the Authorization header of your API requests:
Access tokens expire after the time specified in the “expires_in” field. Your application should request a new token when the current one expires.
Obtaining OAuth Credentials
OAuth client credentials are provided to partners who need access to customer-facing APIs. To request credentials:
- Contact our Partner Integrations Team
- Provide details about your integration use case
- Complete the security review process
- Receive your client ID and client secret
API-Specific Authentication
Different APIs may require specific authentication approaches:
Partner APIs
Customer APIs
The Property Transaction Fee API and Referrals API use API key authentication in the apikey header.
Security Best Practices
- Store API keys and client secrets securely
- Implement proper key rotation procedures
- Use environment variables for storing sensitive credentials
- Never hardcode credentials in your application
- Implement rate limiting and monitoring for unusual activity
- Use HTTPS for all API requests
For more detailed information about specific API authentication requirements, refer to the individual API documentation.