Objective
- Complete testing of the QwikFix API integration using the documentation and staging environment provided by QwikFix.
- Register an account on the QwikFix staging sign-up, obtain a Bearer token, and test the authenticated endpoints described in the API documentation.
- Capture permission issues, endpoint errors, or integration gaps so they can be resolved with the provider before going live.
- Unblock the QwikFix integration and validate the connection on both sides before rollout.
- Validate the intended product flow for the hybrid QwikFix and Thumbtack journey so the integration supports the expected user-facing behavior.
Background
- Users need to finish testing the QwikFix API integration with the provided docs and staging environment.
- Completing this testing unblocks the QwikFix integration and ensures both sides can validate the connection and fix issues before rollout.
- The staging registration link and API documentation are attached to this issue.
- The intended repair flow is a hybrid model where users can choose between QwikFix and Thumbtack based on role and timing.
- Buyer agents want a fast quote path immediately, while the downstream repair path may still route through Thumbtack depending on who is actually handling repairs.
Scope
- Testing: Register on QwikFix staging using the attached registration link, generate a Bearer token, and exercise the authenticated API endpoints per the provided documentation. Document any permission errors, non-200 responses, or missing/incorrect behavior.
- Flow validation: Confirm the API supports the intended user journey when a user clicks the repair action and is presented with two pathways.
- QwikFix should support a fast quote path.
- Thumbtack should remain available as the alternate repair path.
- Quote scope validation: Confirm the integration supports both quote-source options:
- sending selected repair-list items only
- sending the full report
- UX-dependent integration checks: Validate any data or endpoint behavior needed for:
- a modal that presents the two pathways with concise pros and cons
- a confirmation step before sending a QwikFix request
- any toggles or backend configuration needed so this flow is not turned on for every report by default
- Handoff: Share findings such as permission issues, missing fields, unsupported quote scopes, or endpoint-related errors with the provider or internal team so they can be addressed before production.
Additional context from related QuickFix work
- The current product direction is to keep QwikFix and Thumbtack in the same repair journey rather than treating them as separate unrelated features.
- The product needs to support choosing whether QwikFix receives the full report or only the selected items from the repair list.
- The integration may need supporting backend work to connect the correct QuickFix account and ensure the experience can be enabled selectively.
