FAQ
Common questions about accounts, authentication, orders, vendors, payments, integrations, and coming-soon programmatic access.
Accounts and access
Can a Client Admin create an account without support?
Yes. For the supported client-admin onboarding flow, account creation is self-serve through the signup endpoint:
After the account exists, invite team members and assign roles that match their operational responsibilities.
Do these docs use API keys?
No. OmniValVMS uses sign-in and bearer-token authentication today.
API keys, a developer portal, and a dedicated sandbox are planned but not available yet.
What should I do when my token expires?
Refresh it. For reads and clearly idempotent operations, retry the original request once after refresh:
If refresh fails, sign in again.
For activation, assignment, QC/revision, payment, and UCDP/EAD submission actions, reload the order and check history before replaying the write.
Orders
Why can't I activate an order?
Activation starts the real operational lifecycle and SLA tracking, so the order must have all required data first. Check loan, property, contacts, product, payment, and any required documents before activating.
Why can't I assign a vendor?
Vendor assignment is constrained by eligibility: client panel, product, region, capacity, licensing, and order state. If an assignment fails, reload the order and verify the vendor is eligible for that exact product and location.
Can an order skip directly to payment?
No. Payment is gated until delivery and approval are complete. This prevents charging or paying out before the appraisal deliverable is accepted.
Where do I troubleshoot an order that looks stuck?
Start with order history, then inspect specialized logs depending on the issue:
| Problem | Start here |
|---|---|
| Status did not change | |
| Report or revision question | |
| Payment question | |
| Automation question |
Vendors and panels
Is vendor onboarding self-signup?
These guides describe vendor onboarding from the client and operations lens: recruiting vendors, maintaining panels, coverage, products, and fees. They do not describe a vendor-portal self-signup flow.
What determines vendor eligibility?
Eligibility depends on panel membership, coverage, product qualifications, license/compliance requirements, capacity, and client-specific rules.
Integrations
Can I configure outbound webhooks myself?
Not yet. OmniValVMS processes inbound partner webhooks today, but a self-service outbound webhook subscription system is planned for future programmatic access.
Is there a sandbox?
Not available yet. A dedicated sandbox with synthetic data is planned with the developer portal and API-key model. Until then, these docs avoid fake sandbox credentials or sample keys.