API validation
Schema-checked endpoints validate requests at the API boundary.
Security and data
Review how credentials, team access and product data fit into your Claimr integration. Use this overview to identify what your team needs to confirm before launch.
Three areas to review
Who can act, and which credentials do they use?
What information is collected, retained and shared?
How are product events and requests validated?
Documented controls
Confirm scope, availability and responsibilities with the team for your intended setup. This overview is not an independent security assessment.
Schema-checked endpoints validate requests at the API boundary.
Keep organization API keys and MCP secrets in trusted server-side integrations, outside browser code.
Rate limiting and request validation apply to abuse-sensitive endpoints. Confirm the limits relevant to your integration.
Request IDs on API responses help your team trace requests and investigate issues.
Role-based access controls govern team and campaign management. Review the permissions each team member needs.
Review the scope of data export and deletion controls for the information your program collects.
Your integration review
Share the product you are connecting, the data it needs and your evaluation requirements. Agree on the responsibilities for your setup before connecting production data.
Identify the events, user information and connected services involved in your program.
List the people and systems that need access, including any assistant using MCP.
Discuss retention, export and deletion requirements, along with the evidence your reviewers need.
Supporting information
Explore the integration guides and published policies relevant to your setup.
Review event handling and the connection to your product.
Review the account permissions and actions available to your assistant.
The public list is a draft. Contact the team for current provider details.
Read how Claimr describes its handling of personal information.