Get Sign up information

Retrieve the Sign Up information of the user

GET /admin/userSignUp

Get Sign up information

cURL

curl --request GET \
  --url https://api.qovery.com/admin/userSignUp \
  --header 'Authorization: Bearer <token>'

200

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "created_at": "2023-11-07T05:31:56Z",
  "first_name": "<string>",
  "last_name": "<string>",
  "user_email": "<string>",
  "type_of_use": "PERSONAL",
  "qovery_usage": "<string>",
  "updated_at": "2023-11-07T05:31:56Z",
  "company_name": "<string>",
  "company_size": "1-10",
  "user_role": "<string>",
  "qovery_usage_other": "<string>",
  "user_questions": "<string>",
  "current_step": "<string>",
  "dx_auth": true,
  "infrastructure_hosting": "<string>"
}

Authorizations

bearerAuthApiKeyAuth

Authorization · string · header · required

JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '

Response

200

application/json

If a previous sign up request for the same user has been found, the information is returned in the payload

id · string<uuid> · required · read-only

created_at · string<date-time> · required · read-only

first_name · string · required

last_name · string · required

user_email · string · required

type_of_use · enum<string> · required

Available options: PERSONAL, SCHOOL, WORK

qovery_usage · string · required

updated_at · string<date-time> · read-only

company_name · string | null

company_size · enum<string>

Available options: 1-10, 11-50, 51-200, 201-500, 500+

user_role · string | null

qovery_usage_other · string | null

user_questions · string | null

current_step · string | null

dx_auth · boolean | null

infrastructure_hosting · string | null