Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Heya, @ef4b1618a83246338d8eff880389a8
Yes, this can be considered as docs inconsistency, and your observation is correct. I will try to chase this internally as well.
Regards
Hi there,
I might be mistaken, but this looks like a documentation mismatch rather than something you’re doing wrong. Under the hood, DigitalOcean Functions are based on Apache OpenWhisk, and X-Require-Whisk-Auth is the header that is actually enforced at runtime.
The UI and some docs mention X-Function-Auth, but in practice the platform still expects X-Require-Whisk-Auth, which explains why one works and the other returns 401.
So yes, it would make sense for the docs to be updated or clarified. In the meantime, using X-Require-Whisk-Auth is the correct approach if that’s what’s working for your function.