¶ Profile

The Profile endpoint returns the profile of the authenticated driver. A profile includes information such as name, email, rating, and activation status.

¶ Resource

/v1/partners/me

¶ HTTP Method

GET

¶ Access Method

Authorization Code

¶ Required scopes

Primary - partner.accounts
Optional - partner.accounts.personal_info, partner.accounts.personal_info.cpf, partner.accounts.compliance_info

¶ Example Request

curl "https://api.uber.com/v1/partners/me" \
  -H "Authorization: Bearer <TOKEN>"

¶ Example Response

Status-code: 200 OK
{
    "driver_id":"8LvWuRAq2511gmr8EMkovekFNa2848lyMaQevIto-aXmnK9oKNRtfTxYLgPq9OSt8EzAu5pDB7XiaQIrcp-zXgOA5EyK4h00U6D1o7aZpXIQah--U77Eh7LEBiksj2rahB==",
    "first_name":"Uber",
    "last_name":"Tester",
    "email":"uber.developer+tester@example.com",
    "phone_number":"+14155550000",
    "picture":"https://d1w2poirtb3as9.cloudfront.net/16ce502f4767f17b120e.png",
    "rating":5,
    "date_of_birth":"1992-09-09",
    "activation_status": "active",
    "promo_code": "a1smkkps",
    "encrypted_symmetric_key":"CAPDVS9BS18iAAQs+WmS18ynsEsjpFNW5vTeVWwlDvTe7D==",
    "driving_license":{
        "encrypted_license_number":"License number encrypted by AES symmetric key",
        "state":"License state",
        "expiration_date":"License expiration date"
    },
    "encrypted_national_identifier":"National Identifier encrypted by AES symmetric key",
    "partner_role": "driver",
    "city_name": "San Francisco",
    "city_identifier": 1
}

¶ Response Fields

¶ Additional fields available

¶ Additional fields available - Driving License

¶ Additional fields available - Financial Product

¶ Additional fields available - Compliance Info

¶ Driver Compliance Flags

¶ Endpoint Specific Errors

¶ Encryption/decryption process

All drivers’ personal identifier exposed through the API needs to be encrypted through a standard encryption process. The details about the encryption and decryption process is mentioned below -

Prerequisite

• 3rd party will generate the RSA public-private key pair (2048 bit key size) and share the public key with Uber through an encrypted channel (Your Uber POC will connect you to the engineering team).

Encryption

• Uber will generate an AES symmetric key

• This symmetric key will be used to encrypt the driver identifiers. RSA is not directly used because it is non-performant for large objects. AES is more efficient for those cases.

• The driver’s personal identifier will be encrypted using the above mentioned symmetric key by ‘aes-256-gcm’ algorithm. GCM mode is used to ensure integrity of the payload. In the encrypted payload, first 12 bytes contains the IV and rest contains the data.

• The symmetric key will be encrypted using the pre supplied RSA public key and RSA-OAEP algorithm.

• Encrypted symmetric key will be added in the API response as encrypted_symmetric_key field. All other encrypted fields in the API response will start with ‘encrypted_’ prefix.

Decryption

• 3rd party will first decrypt the encrypted AES symmetric key using their RSA private key.

• This decrypted AES key will be used to decrypt the encrypted data fields.