Navigation (menus, bookmarks, pages, filters)Get the create menu

Get the create menu

Returns the caller's create menu: the "New ..." entries (new project, new invoice, new customer ...) the caller may open, grouped by area.

Despite the action name, this is a READ: it creates nothing. It returns the create menu (the '+ New' menu of the web app): group headings per area whose SubMenus are the 'New ...' pages the caller may open. Entries carry Type Main. Group headings have no page, so they carry only Name, Type, IsParent and SubMenus. Names are always English.

Use it to:

Not for:

  • Creating anything - the entries only link to the pages that create records

Behaviour:

  • Idempotent.
  • Safe to retry.

Next: POST /v2/bookmarks

See also: GET /v2/menus/main, GET /v2/menus/create, GET /v2/menus/page-settings, GET /v2/menus/personal-settings, GET /v2/menus/system-administration, GET /v2/pages/design-seven

Not yet documented: behaviour → consistency.

curl -X GET "https://app3.timelog.com/your-account/api/v2/menus/create" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Entities": [
    {
      "Properties": {
        "PageId": "null",
        "Name": "John Doe",
        "Type": "Main",
        "IsParent": true,
        "PageUrl": "null",
        "PageIdentifier": "null",
        "PageType": "null",
        "PageVersion": "null",
        "SubMenus": "null"
      },
      "Links": [
        {
          "Href": "example_string",
          "Rel": "example_string"
        }
      ],
      "Actions": [
        {}
      ]
    }
  ],
  "Links": [
    {
      "Href": "example_string",
      "Rel": "example_string"
    }
  ]
}
GET
/v2/menus/create
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).

The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.

Not yet documented: how to obtain a token.

Not yet documented: token lifetime.

Responses

Entitiesarray

Omitted (not []) when the list is empty.

Linksarray