Add New Journal Cat

Create a journal category — a folder in the chart of accounts that groups other categories and posting accounts.

This endpoint creates categories only. To create a posting account that journal entries can be booked to, use Add New Journal Account instead; an account_type sent in this request is ignored.

Required: code and name.

code must be numeric, and it must not already be used by another category or by a journal account — codes are shared across both. Use GET All Journal Cats and GET All Journal Accounts to find a free code; by convention a child's code extends its parent's (a child of 5 is numbered 51, 52, …).

A code that is already in use does not return an error. The request answers with 302 and a Location header pointing at the chart-of-accounts page, and no JSON body — so check that the code is free before posting, and configure your client not to follow redirects for this call.

Omit journal_cat_id to create a top-level category, or set it to the reference of the parent category to nest this one beneath it.

Only the JournalCat object is read from the request body; any other top-level object is ignored. Content-Type must be application/json; another content type, or a body that is not valid JSON, returns 500.

Do not send id when creating. If it holds the reference of an existing category, that category is overwritten instead of a new one being created. Use the Edit Journal Cats endpoint to change an existing category.

Requires the Manage Journal Accounts permission.

On success the endpoint responds with 202 Accepted and the reference of the new category.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location --globoff 'https://.daftara.com/api2/journal_cats' \ --header 'Accept: application/json' \ --header 'apikey: ' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "JournalCat": { "name": "Test Category", "code": "1" } }'

Request

Responses