Service Registration Process
Before your application can send notifications through ATP, you must register your service with the ATP server. This one-time process establishes your service identity, configures response handling, and sets up security credentials.Understanding Service Registration
Service registration serves several critical purposes:- Service Identity - Establishes a unique identity for your service
- Response Handling - Configures how you’ll receive user responses
- Security - Sets up authentication and verification mechanisms
- User Experience - Provides details about your service to display to users
service_id
that’s used for all future interactions with the ATP system.
Registration Requirements
Before registering, make sure you have:- A publicly accessible webhook endpoint to receive responses
- A service name and description that clearly identifies your service
- An icon URL for visual identification (optional but recommended)
- A webhook secret for verifying incoming webhooks
Creating Your Webhook Endpoint
Your webhook endpoint must:- Be publicly accessible (HTTPS required for production)
- Respond with a
200 OK
status within 5 seconds - Handle POST requests with a JSON payload
- Verify webhook signatures for security
Registering Your Service
Once your webhook endpoint is ready, you can register your service using your ATP client:Python
JavaScript/Node.js
Environment Configuration
After registering your service, you should configure your environment with the obtained credentials:Development vs. Production
ATP supports separate environments for development and production. Use different API keys and configurations for each:Configuration Best Practices
- Never hardcode API keys or secrets in your application code
- Use environment-specific configuration for different deployment environments
- Rotate webhook secrets periodically to enhance security
- Use a secrets management solution for production environments
- Always verify webhook signatures to prevent tampering
Verification Notification
After registration, it’s good practice to send a verification notification to ensure everything is working properly:Webhook Testing
To verify your webhook handling, you can use the ATP test client to simulate responses:Updating Service Registration
If you need to update your service details after registration (e.g., changing the webhook URL or description), use the update method:Webhook Security
Securing your webhook endpoint is critical. Always verify incoming requests using the signature header:- Use HTTPS for your webhook endpoint
- Implement rate limiting to prevent abuse
- Validate the payload format and values before processing
- Keep your webhook secret secure and rotate it periodically
- Implement logging for security monitoring
Verification: Knowledge Check
Before proceeding, let’s verify your understanding of the service registration process: If you understand these concepts and have successfully registered your service, you’re ready to start sending notifications.Next Steps
Now that your service is registered and configured, you’re ready to start creating and sending notifications to your users.Creating Notifications
Learn how to design and send effective notifications