Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex AI Studio
    • About Yandex AI Studio
    • Yandex Workflows
    • Quotas and limits
    • Terms and definitions
  • Compatibility with OpenAI
  • Access management
  • Pricing policy
  • Audit Trails events
  • Public materials
  • Release notes
    • Error codes
    • Request headers for troubleshooting

In this article:

  • Request headers
  • Examples
  • Response headers
  1. Troubleshooting
  2. Request headers for troubleshooting

Request headers for troubleshooting in Yandex AI Studio

Written by
Yandex Cloud
Improved by
amatol
Updated at September 26, 2025
  • Request headers
    • Examples
  • Response headers

If something went wrong while sending API requests and you need help, contact technical support.

The support team will solve your issue faster if you use advanced HTTP request and response headers.

Request headersRequest headers

When sending HTTP requests, use the following headers:

  • x-client-request-id is a unique request ID. We recommend using a UUID. Send this ID to the technical support team to help us find a specific request in the system and assist you.

    You can generate a UUID either online or through the library for the programming language you use.

  • x-data-logging-enabled: Flag that allows saving the data provided by the user in the request.

    By default, all requests to AI Studio are logged. Logging will help resolve your issue if you also specify the request ID when contacting support. You can disable logging if you need to include sensitive information in your request.

ExamplesExamples

You can use the headers below to locate your asynchronous query to a model:

cURL
export FOLDER_ID=<folder_ID>
export IAM_TOKEN=<IAM_token>
curl \
  --request POST \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer ${IAM_TOKEN}" \
  --header "x-folder-id: ${FOLDER_ID}" \
  --data "@<path_to_JSON_file>" \
  "https://llm.api.cloud.yandex.net/foundationModels/v1/completionAsync"

Where:

  • FOLDER_ID: ID of the folder for which your account has the ai.languageModels.user role or higher.
  • IAM_TOKEN: IAM token you got before you started.

Response headersResponse headers

Each server response contains headers that provide even more information about the request execution:

  • x-request-id: Unique response ID
  • x-server-trace-id: Unique request execution log ID

To get the x-request-id and x-server-trace-id values, your application must log server response headers.

You can find an example of implementing access to gRPC headers in the grpc-go documentation.

Was the article helpful?

Previous
Error codes
© 2025 Direct Cursus Technology L.L.C.