Skip to main content

API v2: Habitify API V2 key returns 401 on /journal and /v2/journal returns 404

Bug Report

I generated a new Habitify API V2 key from the mobile app on May 8, 2026.

I tested the API as follows:

  1. GET https://api.habitify.me/journal?target_date=2026-05-08&order_by=priority Header: Authorization: <raw key> Result: 401

  2. GET https://api.habitify.me/journal?target_date=2026-05-08&order_by=priority Header: Authorization: Bearer <raw key> Result: 401

  3. GET https://api.habitify.me/v2/journal?target_date=2026-05-08&order_by=priority Result: 404

Your help article says V2 keys must use the new documentation, but I cannot find a working REST endpoint and auth header format for fetching today's completed habits.

Could you please provide:

  • the exact endpoint

  • the exact auth header format

  • a minimal curl example for API V2

Posted by An Anonymous User ·
Status: Completed4 comments

Comments4

  • Minh Thư

    Team•

    May 28

    Hi!

    For the authentication of current version of Habitify API, here the example request:

  • Minh Thư

    Team•

    May 8

    Hi!

    For the authorization, please check out docs for API V2 here:

    https://api-docs.habitify.me/api.

    If you still have questions, please let us know.

    • onody1984

      •

      May 9

      Thanks. I checked the docs you shared.

      According to your public documentation:

      • Authentication says requests should use the Authorization header with the API key https://docs.habitify.me/authentication

      • Journal says the endpoint is: GET https://api.habitify.me/journal https://docs.habitify.me/core-resources/journal

      So I tested exactly this:

      curl "https://api.habitify.me/journal?target_date=2026-05-08&order_by=priority"
      -H "Authorization: <API_KEY>"

      Result: HTTP 401

      I also tested:

      • Authorization: Bearer <API_KEY> -> HTTP 401

      • https://api.habitify.me/v2/journal -> HTTP 404

      So the issue I facce at the moment is that the public docs and the actual API behavior do not match.

      Could you please provide:

      1. the exact working endpoint for Journal in API V2

      2. the exact required Authorization header format

      3. a minimal working curl example


        Appreciate for your support.