Carrier Vetting Rules | Genlogs API Docs

Authentication

Permissions

The external-api-compliance-rules permission is required to access this endpoint.

Endpoint

Headers

Request Example:

curl --location 'https://api.genlogs.io/customer-compliance-rules' \
--header 'access-token: <your-api-token>' \
--header 'x-api-key: <your-x-api-key>' 

Response:

Response Body:

200 OK

{
    "rules": [
        {
            "id": "18ff81b0-acdd-4a9c-a025-b87b1ee201b0",
            "rule_name": "Observed by GenLogs",
            "status": "enabled",
            "param_values": {
                "date_interval": "2_years",
                "decision_matrix": {
                    "false": "review",
                    "true": "pass"
                },
                "fail_message": false,
                "pass_message": true
            }
        }
    ]
}

401 Forbidden

{
  "detail": {
    "message": "Token is missing",
    "subcode": "TOKEN_MISSING"
  }
}

403 Forbidden

{
    "detail": "User does not have the required permissions to access this resource"
}

Retrieve customer compliance rules

get https://api.genlogs.io/customer-compliance-rules

Returns all compliance rules configured for the authenticated customer. Only rules belonging to the customer associated with the Access-Token are returned. Requires the external-api-compliance-rules permission.

Authorizations

Responses

Code Description Content-Type
200 Compliance rules retrieved successfully. application/json
401 Unauthorized – Invalid or missing Access-Token. application/json
403 Forbidden – User does not have the required permission. application/json
500 Internal Server Error. application/json

GET request example:

GET /customer-compliance-rules HTTP/1.1
Host: api.genlogs.io
Access-Token: YOUR_API_KEY
x-api-key: YOUR_API_KEY
Accept: */*

Test it

200

Compliance rules retrieved successfully.