Update Journal Entries Status (bulk) | Gappify

To facilitate accurate and consistent updates to Gappify JE records (debit and credit pair), Gappify is introducing a new endpoint that will update both the debit/credit lines with a single post call. With the introduction of this new endpoint, this endpoint will be deprecated starting July 1, 2025. Please update your integrations to leverage the new endpoint as soon as possible. Contact support@gappify.com if you need any assistance with this migration.

This endpoint supports the ability to update the status of multiple Gappify JE records based on the posting status within the ERP system. The request requires the use of id as the Gappify record identifier and providing status of the JE (Posted, Failed) along with the appropriate accompanying je_id (when successful) OR error_details (when unsuccessful). This endpoint supports an array of JE updates.

<Note> To facilitate accurate and consistent updates to Gappify JE records (debit and credit pair), Gappify is introducing a [new endpoint](/api-reference/outbound-from-gappify/journal-entries/bulk-update-group-id-qje-transactions) that will update both the debit/credit lines with a single post call. With the introduction of this [new endpoint](/api-reference/outbound-from-gappify/journal-entries/bulk-update-group-id-qje-transactions), this endpoint will be <u>**deprecated starting July 1, 2025**</u>. Please update your integrations to leverage the [new endpoint](/api-reference/outbound-from-gappify/journal-entries/bulk-update-group-id-qje-transactions) as soon as possible. Contact support@gappify.com if you need any assistance with this migration. </Note> This endpoint supports the ability to update the status of multiple Gappify JE records based on the posting status within the ERP system. The request requires the use of `id` as the Gappify record identifier and providing status of the JE (Posted, Failed) along with the appropriate accompanying `je_id` (when successful) OR `error_details` (when unsuccessful). This endpoint supports an array of JE updates.

Authentication

Authorizationstring

API Key authentication via header

Request

This endpoint expects a list of objects.

idintegerRequired

Record Id of the QJE from Gappify's system.

je_idstringRequired

This is required only if the success key is set to true. This is the Record Id of the resulting journal entry in the customer ERP, this value will be used to create link between Gappify QJE and Customer’s journal entry. Upon successful creation in the ERP system, update Gappify with a valid non null value to change status to POSTED.

successbooleanRequired

Sets the status to either “Posted” (if true) or “Failed” if false. This helps to clearly indicate if the customer’s ERP has a successful posting or has had an error.

error_detailsstringOptional

Update the field with error details upon failure to POS JE to the respective system. This is optional when success field is false but can be useful to provide additional context.

Response

Journal entry updated successfully.

request_idUUID

Unique identifier for the request

status"IN_PROGRESS"

Status of the request

1	import requests
2
3	url = "https://api.gappify.com/v1/qje/bulk-update"
4
5	payload = [
6	{
7	"id": 1,
8	"je_id": "je_id",
9	"success": True
10	},
11	{
12	"id": 1,
13	"je_id": "je_id",
14	"success": True
15	}
16	]
17	headers = {
18	"Authorization": "<Bearer>",
19	"Content-Type": "application/json"
20	}
21
22	response = requests.post(url, json=payload, headers=headers)
23
24	print(response.json())

1	{
2	"request_id": "d5e9c84f-c2b2-4bf4-b4b0-7ffd7a9ffc32",
3	"status": "IN_PROGRESS"
4	}

Authentication

Request

Response

Errors