HR core: profiles, onboarding, lifecycle

Accept Prop Trader Consents

Records a prop trader's acceptance of the trader agreement and data consent on their own seat, with request origin.

POSThttps://api.toku.com/hris/accept-prop-trader-consents

Not available to API keys.

curl --request POST \
  --url 'https://api.toku.com/hris/accept-prop-trader-consents' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "roleInOrgId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}'
200 response
{
  "acceptedVersions": [
    "string"
  ]
}

Authorizations

Authorizationstringheaderrequired

Bearer authentication header of the form Bearer <token>, where <token> is an access token from a Toku sign-in. See Authentication in the API reference.

Body

application/json

roleInOrgIdstring<uuid>required
traderAgreementDocumentanyrequired

NOTE(ck): the literal is computed at runtime (JSON.stringify(PROP_TRADER_TERMS)); TGA still enforces the exact value

dataConsentDocumentanyrequired

NOTE(ck): the literal is computed at runtime (JSON.stringify(PROP_TRADER_DATA_CONSENT)); TGA still enforces the exact value

agreeToTraderAgreementanyrequired
agreeToDataConsentanyrequired

Response

200Successful response
successanyrequired
acceptedVersionsstring[]required
400Bad request
401Unauthorized
403Forbidden
404Not found
409Conflict
429Response 429
Was this page helpful? Suggest edits