For AI agents: the documentation index is at /llms.txt, and this page is available as Markdown at /api/account/get-organization-user.md.
Get a user your organization trades for
Returns one of your organization's users, with the wallets held for them.
bearerAuthAuthorizationBearer <JWT>An access token from POST /v1/auth/api-key/token. An organization token lasts one hour and has no refresh token; a personal token can be refreshed.
organization_id*stringYour organization's id: the tm.organization_id claim of an organization token, also shown on the dashboard Overview. The token must be this organization's, or belong to one of its admins.
uuiduser_id*stringuuidThe user your organization trades for
application/json- response
A user the organization trades for
user_id*stringuuidexternal_ref_id*ExternalRefIdThe reference the client names a served user by, unique within the organization. Compared exactly as sent, with no case or format normalisation, so send the same string every time (a UUID in one consistent case).
^[A-Za-z0-9_-]{1,64}$created_at*stringdate-timewallets*array<>Empty only while the wallet step has not completed; re-send the create to finish it.
curl -X GET 'https://api.truemarkets.co/v1/account/organizations/497f6eca-6276-4993-bfeb-53cbbbba6f08/users/497f6eca-6276-4993-bfeb-53cbbbba6f08'{ "user_id": "a169451c-8525-4352-b8ca-070dd449a1a5", "external_ref_id": "string", "created_at": "2019-08-24T14:15:22Z", "wallets": [ { "address": "string", "chain_family": "evm" } ]}Create a user your organization trades for POST
Creates the user your organization trades for under the reference you name them by, with their wallets, or returns the existing one. The wallets are seated with exactly one of your own signer key or a passkey; the passkey signs at Turnkey only and never signs the user in. Re-sending the same request is safe: a 503 means the wallet step did not finish, and repeating the request completes it. Once your organization reaches its user limit a new reference is refused, while re-sending an existing one still works. Use the returned user_id as the TM-On-Behalf-Of value on trading routes.
Get the user's trading setup GET
Returns how the user is set up to trade and to settle.