Get user

GET/v1/admin/users/{userId}

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
userIdpathstringYesUser ID
Query parameters
None.

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200User and budget detailsapplication/json
FieldTypeRequiredDescription
idstringNoUnique identifier.
emailstringNo
namestringNoHuman-readable name.
createdAtstringNoISO 8601 timestamp.
updatedAtstringNoISO 8601 timestamp.
lastLoginAtstringNoISO 8601 timestamp.
isActivebooleanNo
metadataobjectNoFree-form metadata object.
budgetobjectNo
budget.userIdstringNoUser ID.
budget.balancenumberNo
budget.totalSpentnumberNo
budget.dailyLimitnumberNo
budget.monthlyLimitnumberNo
budget.tierstringNo
budget.subscriptionStatusstringNo
budget.subscriptionSourcestringNo
budget.periodStartDatestringNo
budget.periodEndDatestringNo
budget.currentPeriodUsagenumberNo
budget.usagePercentagenumberNo
budget.tierQuotanumberNo
budget.usageBillingEnabledbooleanNo
budget.monthlyResourceSpendLimitnumberNo
budget.pauseOnLimitbooleanNo
budget.resourceEmailAlertsbooleanNo
budget.monthlyResourceSpendnumberNo
budget.monthlyMeteredResourceUsagenumberNo
budget.createdAtstringNoISO 8601 timestamp.
budget.updatedAtstringNoISO 8601 timestamp.
404Resource not foundapplication/json
FieldTypeRequiredDescription
errorstringNo
Get user
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow