Troubleshooting an API Call

Check the token, environment and IDs first, then send RAZE support the details it needs to trace the call.

Runs on: Web browser. Your tech team signs in on the web and builds the integration into your own loan system.

Open the Developer Portal

Quick Reference

Check that the token hasn't expired.

Check the address, service account and codes all belong to one environment.

Check the project ID and inspection ID.

Send support the details listed in step 3.

Before You Start

You have the request and the response from your logs.

You know the time of the call.

Step 1 — Check the Usual Causes

The token

Tokens last an hour. Request a new one and retry.

The environment

The address, the service account and the codes must all belong to the same environment.

The IDs

Use the project ID and inspection ID the create call returned for this inspection.

Step 2 — Document Not Visible to the Inspector

Check the project ID

Confirm the upload went to the right project ID.

Check the inspection

Get the inspection and confirm the document is attached.

Send the details

If it's attached but still not visible to the inspector, contact RAZE support with the document ID and file name.

Step 3 — Send RAZE Support the Details

Include all of these

The environment (Stage or Production), your project GUID, the project ID, the inspection ID, the time of the call, the call you made, the response body or error, and the document file name and document ID if a document is involved.

Tips

DO

•Log every request and response with a timestamp.
•Include the project ID and inspection ID in every support request.
•Retry with a fresh token before you report a failure.

WATCH FOR

•A success response on an upload isn't proof the file is visible.
•Stage and Production credentials don't mix.
•Never send a password or token to support.