AppSignal

Refund Rules

AppSignal does not appear to have publicly available refund policies documented. As a subscription-based APM service with monthly billing based on request volume, standard SaaS practices would likely apply - no refunds for partial months or unused capacity within billing cycles. Billing is based on total monthly request volume across all apps, making partial refunds for unused seats unlikely since pricing is volume-based rather than seat-based.

Credit Policies

No specific credit policies are documented in available materials. Given AppSignal's focus on application monitoring and uptime, they likely offer credits for significant service outages or downtime, but specific SLA terms and credit calculations are not publicly available. Credits for pre-paid unused capacity would be uncommon given their monthly volume-based billing model.

Contractual Terms

Contract terms are not publicly documented. Standard SaaS considerations would include: monthly auto-renewal cycles, potential price increases with notice periods, and cancellation terms. Given the volume-based pricing model, price changes might be tied to usage tier modifications. Cancellation notice periods and data retention policies after cancellation are not specified in available documentation.

Integration Complexity

Technical Notes

AppSignal uses Personal API Tokens (no OAuth2) requiring manual token entry. REST API is well-documented with consistent JSON endpoints using .json extensions. Rate limits are not documented. Authentication via query parameter (?token=). Multiple API types: REST (read), GraphQL (full access), Push API (write). App-level scoping requires app IDs from dashboard URLs. GraphQL API mirrors frontend functionality with introspection available. No API versioning mentioned - breaking changes possible.