Skip to main content
GET
/
2
/
users
/
public_keys
Get public keys for multiple users
curl --request GET \
  --url https://api.x.com/2/users/public_keys \
  --header 'Authorization: Bearer <token>'
{
  "data": {
    "public_key": "<string>",
    "signing_public_key": "<string>",
    "token_map": {
      "key_store_token_map_json": "<string>",
      "max_guess_count": 123,
      "realms": [
        {
          "address": "<string>",
          "realm_id": "<string>",
          "token": "<string>"
        }
      ]
    },
    "version": "<string>"
  },
  "errors": [
    {
      "title": "<string>",
      "type": "<string>",
      "detail": "<string>",
      "status": 123
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.x.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Query Parameters

​
ids
string[]
required

A list of User IDs, comma-separated. You can specify up to 100 IDs.

Required array length: 1 - 100 elements

Unique identifier of this User. This is returned as a string in order to avoid complications with languages and tools that cannot handle large integers.

Pattern: ^[0-9]{1,19}$
​
public_key.fields
enum<string>[]

A comma separated list of PublicKey fields to display. The fields available for a PublicKey object.

Minimum array length: 1
Available options:
juicebox_config,
public_key,
signing_public_key,
version
Example:
[
  "juicebox_config",
  "public_key",
  "signing_public_key",
  "version"
]

Response

The request has succeeded.

​
data
object

Public key information for Chat encryption

​
errors
object[]
Minimum array length: 1

An HTTP Problem Details object, as defined in IETF RFC 7807 (https://tools.ietf.org/html/rfc7807).