Is /api/v3/graphql available? Getting 404 on all v3 endpoints, unable to query dustGenerationStatus.

[TranHuyHiep]

Hi team,
I'm trying to work with the Midnight Indexer API v3, but I’m not sure whether the /api/v3/graphql endpoint is actually available in the current Docker images.

My environment:

• Indexer API images tried:
  • midnightntwrk/indexer-api:3.0.0-alpha.19
  • midnightntwrk/indexer-api:latest
• Midnight node: midnightnetwork/midnight-node:latest
• Chain indexer + wallet: both using latest
  Network: testnet-02

Problem:
Every request to the v3 endpoint results in: 404 Not Found

Endpoints tested:

• /api/v3/graphql → 404
• /api/v3 → 404
• /api/graphql → 404
• /api/v1/graphql → works, but does not include the v3 fields

/api/v1 → OK

curl -v -X POST http://<host_ip>:<port>/api/v3/graphql   -H "Content-Type: applica
tion/json"   -d '{
    "query": "query { block(offset: { height: 3 }) { hash height timestamp protocolVersion }}",
    "variables": {
      "hash": "554bda62777feeb74abb54481a797cf6fd4a5c5a54608e6c8db32ac22bd16dde"
    }
  }'

My result:

> POST /api/v3/graphql HTTP/1.1
> Host: <host_ip>:<port>
> User-Agent: curl/8.5.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 207
> 
< HTTP/1.1 404 Not Found
< vary: origin, access-control-request-method, access-control-request-headers
< access-control-allow-origin: *
< access-control-expose-headers: *
< content-length: 0
< date: Fri, 12 Dec 2025 13:50:58 GMT
< 

Questions

• Has /api/v3/graphql been released in the current Docker images?
• The docs say v3 is the current API, but I cannot find it in the images.

If v3 is available:

• Which exact image tag contains the v3 schema and endpoint?
• Is there any configuration flag required to enable v3 support?

If v3 is not yet deployed:

• Is there an expected release timeline?
• Should we continue using v1 for now?

Thanks team — just want to confirm the status of v3 and the proper way to access the new fields.

[hseeberger]

Hi @TranHuyHiep,

/api/v3/graphql and /api/v3/graphql/ws are the only available endpoints (for queries and WS based subscriptions respectively).

In the above curl response > Host: <host_ip>:<port> looks fishy.

[TranHuyHiep]

Hi @hseeberger ,

Thanks for the clarification.
In the curl example, <host_ip> and are just placeholders.
In my actual request, I replaced them with the real IP address and exposed port of the server where the Midnight indexer API container is running.

For example:
curl -X POST http://<actual_server_ip>:<actual_exposed_port>/api/v3/graphql ...

So the request is definitely hitting the correct host and port of the running container, but /api/v3/graphql still returns 404 Not Found, while /api/v1/graphql works as expected.

Please let me know if there is any additional configuration or image tag I should verify.

Thanks!

[hseeberger]

/v1 is working? Then you might be using an outdated Indexer, v2.x or even older which has API /v1.

Please make sure you are using indexer-api:3.0.0-... which supports /v3.

[TranHuyHiep]

I'm sure I used the image midnightntwrk/indexer-api:3.0.0-alpha.19. Do I need to update both the midnight node and the midnight chain indexer as well?

[hseeberger]

Generally you must use the same version of the Indexer components, i.e. chain-indexer, wallet-indexer and indexer-api. You also must make sure to delete all old state, i.e. start from zero (Postgres and NATS). And yes, there is a compatible Node version: https://github.com/midnightntwrk/midnight-indexer/blob/main/NODE_VERSION.

I am still confused by /v3 giving you 404. 3.0.0-alpha.19 still forwards /v1 to /v3 which we will soon turn off, so it is not surprising that /v1 works. But /v3 should also work (exactly the same).

[TranHuyHiep]

I'm still using Midnight Node with the tag "latest," but I see that Midnight has updated to a new version. I'll try installing the new version and let you know the results.

[hseeberger]

Never use latest, because results are unpredictable.

[cosmir17]

The compatible node version for indexer 3.0.0-alpha.19 is 0.18.0-rc.7 - check the https://github.com/midnightntwrk/midnight-indexer/blob/main/NODE_VERSION file in the repo.

After each test locally, kill postgres and nats docker instances and empty target/data folder before doing next test 🙏

edit : Upto 0.18.0-rc.10 node is compatible with the latest version of indexer v3.0.0-alpha.19 (9573beb)

[TranHuyHiep]

Did I run the configuration correctly? I'm running Midnight Node with image 0.18.0-rc.7 and the environment is testnet-02. I'm running it using the repository https://github.com/midnightntwrk/midnight-node-docker and I'm getting the following error:

thread 'main' panicked at node/src/cfg/mod.rs:346:37:
called `Result::unwrap()` on an `Err` value: ConfigError(Failed to load config testnet-02)
stack backtrace:
   0:     0x61708077a652 - std::backtrace_rs::backtrace::libunwind::trace::h2d45396358f41939
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/../../backtrace/src/backtrace/libunwind.rs:117:9
   1:     0x61708077a652 - std::backtrace_rs::backtrace::trace_unsynchronized::hffcefc0b67f1d6e2
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/../../backtrace/src/backtrace/mod.rs:66:14
   2:     0x61708077a652 - std::sys::backtrace::_print_fmt::hd72f71d23b436b92
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:66:9
   3:     0x61708077a652 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hdcfcb6d4c8489523
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:39:26
   4:     0x6170807a90a3 - core::fmt::rt::Argument::fmt::h2c56b3114963061a
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/fmt/rt.rs:173:76
   5:     0x6170807a90a3 - core::fmt::write::h8a494366950f23bb
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/fmt/mod.rs:1468:25
   6:     0x617080774ef3 - std::io::default_write_fmt::ha27fbccbc65eb6fa
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/io/mod.rs:639:11
   7:     0x617080774ef3 - std::io::Write::write_fmt::h6556609fca33d0b1
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/io/mod.rs:1954:13
   8:     0x61708077a4a2 - std::sys::backtrace::BacktraceLock::print::hb2a626a81e06b2dc
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:42:9
   9:     0x61708077c0ad - std::panicking::default_hook::{{closure}}::h4f78485264f12d10
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:300:27
  10:     0x61708077be8f - std::panicking::default_hook::h2c66fc99e962531d
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:327:9
  11:     0x61708077cac5 - std::panicking::rust_panic_with_hook::h33ac55f64bbd807d
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:833:13
  12:     0x61708077c85a - std::panicking::begin_panic_handler::{{closure}}::h30e7cb89678a57fe
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:706:13
  13:     0x61708077ab59 - std::sys::backtrace::__rust_end_short_backtrace::hed60f27456c16ced
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/sys/backtrace.rs:174:18
  14:     0x61708077c4ed - __rustc[de2ca18b4c54d5b8]::rust_begin_unwind
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:697:5
  15:     0x6170807a5f50 - core::panicking::panic_fmt::h62f63d096dd276af
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/panicking.rs:75:14
  16:     0x6170807a6376 - core::result::unwrap_failed::h95bc3f5a607b2c95
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/result.rs:1765:5
  17:     0x61707c97250e - midnight_node::cfg::Cfg::help::hc31c5f8cfef97360
  18:     0x61707c97646f - midnight_node::command::get_cfg::h6670466d12fdf4d2
  19:     0x61707c9730f6 - midnight_node::command::run::he4d4409ec7df18f0
  20:     0x61707c858a0a - midnight_node::main::h772544e6c7b443ea
  21:     0x61707c856b96 - std::sys::backtrace::__rust_begin_short_backtrace::h5f0a4ad9a9b42de2
  22:     0x61707c854205 - std::rt::lang_start::{{closure}}::hbdcd27d47fdbcf47
  23:     0x617080767820 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h638295a043b40957
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/core/src/ops/function.rs:290:21
  24:     0x617080767820 - std::panicking::catch_unwind::do_call::hbd68098bdea1ca50
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:589:40
  25:     0x617080767820 - std::panicking::catch_unwind::h50591d85bf847c7c
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:552:19
  26:     0x617080767820 - std::panic::catch_unwind::h2487b4c4f2ae22c6
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panic.rs:359:14
  27:     0x617080767820 - std::rt::lang_start_internal::{{closure}}::h61f0945cc6c9a811
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/rt.rs:175:24
  28:     0x617080767820 - std::panicking::catch_unwind::do_call::h34b9c3722acd6bd1
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:589:40
  29:     0x617080767820 - std::panicking::catch_unwind::hf9a822ea043fb0d6
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panicking.rs:552:19
  30:     0x617080767820 - std::panic::catch_unwind::h5b3cac802237ed89
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/panic.rs:359:14
  31:     0x617080767820 - std::rt::lang_start_internal::h34f9328d113fd60a
                               at /rustc/1159e78c4747b02ef996e55082b704c09b970588/library/std/src/rt.rs:171:5
  32:     0x61707c858a35 - main
  33:     0x7d66c6375ca8 - <unknown>
  34:     0x7d66c6375d65 - __libc_start_main
  35:     0x61707c854121 - _start
  36:                0x0 - <unknown>```

[hseeberger]

@TranHuyHiep, please ask this question in the respective repository (midnight-node-docker), because it touches way more than the Indexer.

[TranHuyHiep]

@cosmir17 I saw in the release document at https://docs.midnight.network/relnotes/overview that it doesn’t list the node version for indexer 3.0.0-alpha.19 and indexer version 0.18.0-rc.7. How can I find a guide to run this version?