Fetch Estimates
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Retrieve the authenticated customer’s customer estimates.
Where to goExternal backend → GET /proplix_api_gateway/portal_api/me/estimates
Before you start
- Verify the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What this guide helps you do
Retrieve the authenticated customer’s customer estimates. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to External backend → GET /proplix_api_gateway/portal_api/me/estimates.
- Find the record, endpoint, field or action used to fetch estimates.
- Complete the displayed values exactly as described in this guide.
- Select the available save, submit, send, upload, create, update or confirm action.
- Return to the related register, portal, activity log or API response and verify the expected result.
Fields and options
Sectionestimates
ReturnsCustomer estimates.
Rules and limits
- The portal profile must allow the section.
- Core CRM/client portal permissions and client ownership still apply.
Check it worked
- The fetch estimates workflow completes without a validation, permission, ownership or availability error.
- The related record, portal view, activity entry, notification log or API response shows the expected state.
- Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.
Security, privacy and operational checks
- Use controlled test records and non-production credentials before wider rollout.
- Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.
Related guides
Was this guide useful?Your response is stored only in this browser.