Submits a file for deidentification

Submit a file for De-identification

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
enum
required

Type of validation to perform.

Allowed:
Body Params
file
required

The X12 file to remediate (application/edi-x12)

file

The choices JSON file to use de-identifying (application/json)

boolean

0 for Basic method, 1 for Advanced method

Headers
string
required

Most endpoints within the API require a header named "account" which contains the account name from the accounts field in the /userinfo object for which the endpoint is being performed. A user might be associated with multiple accounts and this header determines which account to use.

string
required

The authorization header is required to authenticate requests to this endpoint. Format the header value as Bearer {token}, where {token} is your authentication token.When determining if a user is authorized to perform an action for a given endpoint, the authorization header value and the account header value are used to determine the account for which the request is being made. If the user has a service listed that matches the capability for the endpoint and a role under that service to perform the action, the request is granted. Otherwise, a 401 is returned.Using your {token}, you can perform a GET request to the /users endpoint to see the services and roles for which the user is provisioned. Check with your organization administrator if additional services or roles are needed.

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json