This API implemention will return an Error object when the FullContact response
This API implementation will return an Error object when the FullContact response
is returned without a `status: 200` or `status: 202` so it could be that your operation is queued for processing. That's why all returned error's have a `status` property which
is returned without a `status: 200` or `status: 202` so it could be that your operation is queued for processing. That's why all returned error's have a `status` property which
the returned status code (unless it's a parse error or a generic error). So just
the returned status code (unless it's a parse error or a generic error). So just
because you got an error, it doesn't mean that your request has failed.
because you got an error, it doesn't mean that your request has failed.
The CI testing happens with a free api key that has limits to the calls it can do to FullContact. If you see the tests fail make sure it is because of failing tests not exeeding rate limit.
The CI testing happens with a free api key that has limits to the calls it can do to FullContact. If you see the tests fail make sure it is because of failing tests not exceeding rate limit.
The tests are written against the live FullContact API. They can be ran using:
The tests are written against the live FullContact API. They can be ran using: