Help for your team

Partner Support

Open your tools, find an answer, or get help with access and integrations.

API Documentation

Portal: browser access with your assigned email login.

API: read-only search for server-side integrations.

Browser portal

Portal troubleshooting

Choose the issue you are seeing for steps to try before contacting support.

I cannot sign in
  1. Use the email login assigned by your organization. Check the email address for typos before trying again.
  2. If you have forgotten your password, select Forgot Password? on the portal login screen.
  3. If your account is new, your organization has changed, or access still fails, contact Ratespedia with your organization name and portal email.
My password reset code is missing or expired
  1. Enter the email used for your portal login in Forgot Password? and check that inbox, including its spam or junk folder.
  2. Use the 6-digit verification code from the reset email. Codes expire after 15 minutes; request a new code if yours has expired.
  3. Complete the password requirements shown on screen, then sign in with your new password. If the email never arrives, contact Ratespedia to check your access.
The portal asks me to set a permanent password
  1. A one-time setup link or a temporary password can require you to create a permanent password before using the portal.
  2. Complete the setup screen and follow its password requirements. If you keep returning to that screen after saving, contact Ratespedia with the error text.
Agree and continue is disabled
  1. Read the entire user agreement by scrolling inside the agreement panel to its end.
  2. The consent checkbox becomes available after you reach the end. Check it, then select Agree and continue.
  3. If the agreement fails to load or the controls remain unavailable after those steps, contact support with the error text and your browser details.
No record was found
  1. Enter the record number from the mail piece in the Record number field. Check for missing characters or a typing error.
  2. Make sure you are using the intended organization account. The portal searches records available to that account.
  3. If the number is correct and the record is still missing, ask Ratespedia to confirm that the expected record is available to your account.
CRM delivery is unavailable or record details are not showing
  1. A successful lookup initially shows only 1 record found. Enter a valid US phone number to enable the Bonzo / CRM delivery action.
  2. Full customer and loan details appear only after the CRM confirms delivery. A rejected delivery or timeout does not reveal those details.
  3. Check the phone number and keep any delivery error text. If delivery still fails, contact support so the response flow can be checked.
Go to portal login

Direct integrations

API troubleshooting

Start with the HTTP status and error code returned by your request. The API documentation has the full parameter and response reference.

401Authentication
Send one supported authentication header: Authorization: Bearer <token> or x-api-key: <token>. For production requests, confirm with Ratespedia that the key is active for the correct environment.
400Invalid request
Check the documented query parameters and filter formats. Send only one authentication header. If the cursor is invalid, restart pagination from the first page.
405Read-only API
Remove the write request. Customer API keys support retrieval only; use GET /api/mailed-records/search for production search.
429Rate limit or quota
For rate_limited, wait at least one minute before retrying and reduce the request rate. For a daily, weekly or monthly quota error, wait for the next quota window or contact Ratespedia to review your account limits.
500Service error
Retry later. If the error persists, contact support with the endpoint, status, error code and time of the request. Redact credentials and personal data from logs.

No search results? Broaden the API filters or confirm that the expected records are available to your account.

Testing your setup? Use the configuration test endpoint described in the documentation. It checks request format without touching production records and does not validate an active production key.

View the full API reference

Frequently asked questions

Who can use the Mailed Records Portal?

The portal is for approved partner accounts. Use the email login assigned by your organization. If you need access or a team member needs help getting set up, contact Ratespedia with the organization name and intended portal email.

Do I need an API key to use the portal?

No. The portal uses your assigned email login. API keys are for direct server-side integrations and should stay on your server, not in browser code or URLs.

Why does a lookup show only “1 record found”?

The portal uses a two-stage lookup. It confirms a record was found first, then requires a valid US phone number and confirmed Bonzo / CRM delivery before showing full customer and loan details.

Can the customer API update or delete records?

No. Customer API keys provide read-only search access. Write requests receive a 405 read_only_api response. Authenticated portal and CRM workflows are separate from customer API access.

Does a successful configuration test validate my production API key?

No. The test endpoint checks header format and request parameters without accessing production records. A test response with credentialValidated: false does not establish that the key is active. Production endpoints validate the actual key.

Are the iPhone and Android apps available yet?

The iPhone and Android apps are in development and are marked Coming soon. Use the browser portal for current access.

Still need help?

Contact Ratespedia for account access, quota questions or integration support.

Include these details

  • Your organization name and portal login email.
  • The task you were trying to complete, the error text and when it happened, including your time zone.
  • Your browser and device, or the API endpoint, HTTP status and error code.

Remove passwords, API keys, verification codes and borrower personal data from messages, screenshots and logs.