Resolve problems with a DEA registration verification

After a verification is executed we sometimes are uncertain about the results we get from the source. For example when the name of the DEA registration does not match the name that was used for the provider. In such cases we mark the verification status as NeedsReview. It is expected that this status is resolved by the end user. The resolution can be patched by using this endpoint.

Request
path Parameters
providerId
required
string <uuid>

The identifier describing the provider that holds the DEA registration.

registrationNumber
required
string

The DEA registration number that has a verification problem.

verificationId
required
string <uuid>

The identifier describing the verification that needs to be patched.

Request Body schema: application/json
status
string

The correct status for this verification.

Enum: "Found" "Failed" "NeedsReview" "NotFound" "Pending" "Working"
Responses
200

Success

400

Bad Request

401

Unauthorized

402

Client Error

403

Forbidden

404

Not Found

409

Conflict

500

Server Error

patch/providers/{providerId}/dea/{registrationNumber}/verifications/{verificationId}
Request samples
application/json
{
  • "status": "Found"
}
Response samples
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "timestamp": "2019-08-24T14:15:22Z",
  • "lastUpdated": "2019-08-24T14:15:22Z",
  • "lastSync": "2019-08-24T14:15:22Z",
  • "status": "Found",
  • "originalStatus": "Found",
  • "results": {
    },
  • "deaxResults": {
    }
}