Updated 2026-11-20

DeepSeek V4.1 Model ID Migration Guide

For V4.1 Flash on the official DeepSeek API, set the model field to deepseek-flash. If your application intentionally calls V4 Pro, keep deepseek-v4-pro. Identify which value your application actually sends before changing a configuration file.

Look up the value in your configuration

These mappings apply to api.deepseek.com. A proxy, another API provider or a locally hosted server may expose different names. Check the base URL alongside the model field.

Official API configuration names as of November 20, 2026DeepSeek's current API models and compatibility names
Current value or labelWhat it meansValue to send
deepseek-flashPreferred hosted Flash ID, currently serving Flash-1017deepseek-flash
deepseek-v4-flashOlder Flash name accepted for compatibilitydeepseek-flash
deepseek-v4-flash-vision-expFormer experimental vision name, now routed to the same Flash checkpointdeepseek-flash
deepseek-v4-proActive hosted V4 Pro ID, currently serving V4-Pro-0813deepseek-v4-pro
DeepSeek-V4.1-Flash-1017Dated Flash checkpoint label used in release notes and weight repositoriesdeepseek-flash
DeepSeek V4.1 ProA future Pro release mentioned by DeepSeekNo public API ID listed

Change the field your client sends

In a Chat Completions request, edit the top-level model field. In an SDK, find the model argument passed to the completion call. If it comes from an environment variable or an agent profile, edit that source and reload the process that reads it. An environment variable only takes effect if the client reads it.

For example, a client configured for the former Flash vision route needs a one-line change. The same Flash ID handles text and images. Keep the existing message content and authentication when changing this field on the same official endpoint.

-  "model": "deepseek-v4-flash-vision-exp",
+  "model": "deepseek-flash",

Check the IDs available to your key

With your official API key in DEEPSEEK_API_KEY, request the model list from the same host your application uses. Look for the desired ID under data[].id. To map the ID to a dated checkpoint, use DeepSeek's model details table.

If the ID appears in the list but your tool rejects it before sending a request, check the tool's provider profile and allowed-model list. If the request reaches a different host, consult the documentation for that host. The older deepseek-chat and deepseek-reasoner names have a separate migration history.

bash
curl --fail --silent --show-error https://api.deepseek.com/models \
  -H "Authorization: Bearer $DEEPSEEK_API_KEY"

FAQ

Does switching back to an old Flash alias restore the old model?

Both documented aliases now route to Flash-1017 and are billed at the Flash rate. Restoring the old string changes the request spelling only.

Should I rename deepseek-v4-pro during this migration?

Keep that ID if the application needs the current V4 Pro model. The September changelog records that DeepSeek continued Pro service. Use the current model table and the V4.1 Pro status page when a future Pro version is announced.