Phonematch web service – error codes

When utilising the Phonematch web service, there is a possibility that you will experience errors at some point. The errors that could occur during the authentication process are highlighted below:

Authentication Errors

error Service response Response Content
Consumer key is not valid 401 HTTP response code: HTTP/1.1 401 Unauthorised oauth_problem=consumer_key_unknown
Oauth signature is not valid 401 HTTP response code: HTTP/1.1 401 Unauthorised oauth_problem=signature_invalid
Oauth nonce has been used previously 401 HTTP response code: HTTP/1.1 401 Unauthorised oauth_problem=nonce_used
Timestamp sent in request is too old (over 5 minutes) 401 HTTP response code: HTTP/1.1 401 Unauthorised ooauth_problem=timestamp_refused

Once authenticated, you may experience service errors. A service error is indicated by the presence of the error response parameter. Additionally, the errors property will contain a list of error messages.

Examples of errors and the error response parameters and error properties returned are highlighted below:

Status Codes

These are the possible outputs for Status

Code Description
100 Search returned successfully.
130 Authentication - Consumer key is not valid.
131 Authentication - Oauth signature is not valid.
132 Authentication - Oauth nonce has been used previously.
133 Authentication - Timestamp sent in request is too old (over 5 minutes).
140 Insufficient credits to perform search.
141 User unable to perform search.
142 Invalid format for landline service option.
143 Invalid format for mobile service option.
144 Invalid format for ignore numbers option.
150 No forename supplied.
151 No surname supplied.
152 No postcode supplied.
153 Invalid Input.
160 Multiple fields not supplied.
170 Address Not Matched.
190 Internal service error.

If you have any issues related to errors, or need assistance, please do not hesitate to contact our web service support team.