Get agent details

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Get Agent Profile By ID

Returns the full profile of a specific agent within the ISO associated with the authenticated API user. The profile includes the agent's name, payout number, office details, username, email, and phone. This information is typically used to validate agent details before associating them with a merchant application.

Endpoint

GET /api/v1/agent/profile

Authentication

Basic HTTP Authentication required.
Encode username:password in Base64 and pass in the Authorization header:

Authorization: Basic {base64(username:password)}

When to use

Use this endpoint when you need to look up or confirm the details of a specific agent before associating them with a merchant. It is commonly called after GET /api/v1/agentProfiles to fetch the full detail record for a specific entry from the list. This is also useful for displaying agent information in a boarding portal UI or for audit and reporting purposes.

Query Parameters

ParameterTypeRequiredDescription
idinteger (int32)YesThe agent profile ID to retrieve

Response

200 OK

FieldTypeDescription
data.idintegerThe agent profile ID
data.namestringCombined display name (typically payoutNumber + agentName)
data.payoutNumberstringThe agent's payout number used for commission distribution
data.agentIdintegerThe unique identifier of the underlying agent record
data.agentNamestringThe agent's full name
data.agentOfficeIdintegerID of the agent's office/branch
data.agentOfficeNamestringName of the agent's office/branch
data.agentUserNamestringSystem username for the agent (e.g., iso01074-63018)
data.emailstringAgent's email address
data.phonestringAgent's phone number
statusstringHTTP status label (e.g., OK)
errorstringError message if the lookup failed
warningstringNon-fatal warning message, if any
validationResultsarrayList of field-level validation errors
requestIdintegerUnique identifier for this API request
{
  "data": {
    "id": 4264,
    "name": "1354275284 Maria Santos",
    "payoutNumber": "1354275284",
    "agentId": 63018,
    "agentName": "Maria Santos",
    "agentOfficeId": 1074,
    "agentOfficeName": "Southwest Regional Office",
    "agentUserName": "iso01074-63018",
    "email": "[email protected]",
    "phone": "305-555-0182"
  },
  "status": "OK",
  "error": null,
  "warning": null,
  "validationResults": [],
  "requestId": 91512
}

Error Codes

CodeWhen it happens
400id parameter is missing or not a valid integer
401Invalid or missing Basic Auth credentials
403User does not have permission for this operation
404Agent profile with the specified id not found or not accessible to this ISO
500Internal server error

Common Mistakes

  • Using an id that belongs to an agent outside the authenticated user's ISO — you can only retrieve profiles for agents within your own ISO.
  • Confusing id (agent profile ID) with agentId (the underlying agent record ID) — use the id returned by GET /api/v1/agentProfiles for this endpoint.
  • Expecting phone to always be populated — phone is optional in the agent profile and may be null or empty.

Related Endpoints

  • GET /api/v1/agentProfiles — retrieve all agent profiles for your ISO (use to get valid id values)
  • POST /api/v1/merchant/create — create a merchant and assign an agent using agentProfileId
  • GET /api/v1/GetBoardingSettings — retrieve boarding settings to use alongside the agent profile when creating merchants

Example

curl -X GET "https://hq.staging.netevia.dev/api/v1/agent/profile?id=4264" \
  -H "Authorization: Basic $(echo -n 'username:password' | base64)"
Query Params
int32
required
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

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