Support
Who to write to
integrations@appraisalhost.com reaches our integrations team. Use it for
anything about this API: sandbox access, a call that behaves differently from
this documentation, a webhook that is not arriving, a question about a field, or
a change you would like to see in a future version.
Write in English. We answer on United States business days.
For anything about a specific lender's account rather than the interface itself, the appraisal management company you are integrating for is the right first call: it issues and revokes credentials, decides which of its products a lender may order, sets the fees, and moves the orders.
| Question | Ask |
|---|---|
| Sandbox access, a test lender account, advancing a test order | Our integrations team |
| A response that does not match this documentation | Our integrations team |
| A webhook that is not arriving, or a signature that will not verify | Our integrations team |
| Production credentials, or a credential rotation | The appraisal management company |
| Which products a lender may order, and what they cost | The appraisal management company |
| The status of a specific live order | The appraisal management company |
| A field or an event you need that does not exist yet | Our integrations team |
What to include
The more of this you send, the faster the answer:
- The environment: sandbox or production.
- Your client id. It starts with
cli_and is safe to send. Never send a client secret, a webhook secret or a bearer token. If a secret has been exposed, say so and we will treat it as urgent. - The
correlation_idfrom the response. Every error carries one, and it takes us straight to the request. - The request: method, path, and the body with borrower details removed.
- The response: status code and body.
- The time, with its time zone, and how often it happens.
- What you expected, and which page of this documentation led you to expect it. If our documentation is wrong, that is a defect on our side and we want to know.
For a webhook problem, send the event id from X-AH-Event-Id, or the id from
GET /events, plus what your endpoint returned. GET /events shows you our side
of the story first: the attempt count, the last status we received from you, and
when we will try again.
Requesting sandbox access
Sandbox access is provisioned on request. Send us:
- Your company name and the product you are integrating.
- A technical contact: name, email and time zone.
- The HTTPS URL you want webhooks delivered to during the build, if you have one yet.
- Which order types you need in the sandbox catalog: at least one product on the current report standard, at least one on the prior standard, and a product with an FHA certification requirement if you will place those orders.
We reply with a client id, a client secret and your sandbox order type codes. Full detail is on the Sandbox page.
Reporting something that looks like a security problem
Write to integrations@appraisalhost.com with "security" in the subject line and
tell us what you saw. Do not include another party's data in the report, and do
not test against production. We will confirm receipt, investigate, and tell you
what we found.
Service status
Our integrations team notifies the technical contact on every active credential about planned maintenance, and about any incident that affects the API.
Once your integration is provisioned, put GET /ping in your own monitoring. It
needs no credential, returns no account data, and answers 200 while the API is
serving traffic:
curl -s https://api.appraisalhost.com/v1/ping
{ "status": "ok", "time": "2026-09-17T14:32:05Z" }
If calls are failing and GET /ping answers, the problem is most likely with
your credential, your request or your network path rather than with the service.
Send us the correlation_id and we will tell you which.