Skip to content

Agent Validate

Rate partners can validate an agent email before calling Partner Quote APIs. Use the same x-api-key as /partner/v2/policy/quote and /partner/v2/policy/lead.

Endpoint

Environment URL
Prod POST https://insurance-api.novo.us/account/v1/agent/validate
UAT POST https://insurance-api.uat.novo.us/account/v1/agent/validate

Authentication

Include your partner API key in the x-api-key header (see Get Started).

Request

Field Type Required Description
email string Yes Agent email to validate

The agent user type is implied by the /account/v1/agent/validate path.

Example

1
2
3
4
5
6
curl -X POST 'https://insurance-api.uat.novo.us/account/v1/agent/validate' \
  -H 'x-api-key: {x_api_key}' \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "agent@example.com"
  }'

Response

Success (HTTP 200)

Validation completes with HTTP 200 for both valid and invalid agents. Check data.is_valid.

1
2
3
4
5
6
7
8
{
  "status": "success",
  "message": "User verification success",
  "data": {
    "is_valid": true,
    "agent_id": "agt-123456789"
  }
}

When the agent is not found or not eligible:

1
2
3
4
5
6
7
{
  "status": "success",
  "message": "The specified user_type does not match the account.",
  "data": {
    "is_valid": false
  }
}

Errors

HTTP Body When
400 { "status": "error", "message": "..." } Invalid JSON, missing fields, or invalid email format
403 { "status": "error", "message": "Forbidden" } Missing or invalid API key
500 { "status": "error", "message": "Internal server error" } Upstream error

Notes

  • Call agent validate before Partner Quote when your integration requires a known-good agent id.
  • agent_id is returned in data when is_valid is true.