API ReferenceOutbound from GappifyJournal Entries

Update Journal Entries Status (bulk)

Deprecated

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.

Headers

AuthorizationstringRequired

Request

This endpoint expects a list of objects.
idintegerRequired

Record Id of the QJE from Gappify’s system.

successbooleanRequired

Indicates the status of the JE posting in ERP system:

  • “Posted” if JE creation is successful
  • “Failed” if JE creation is unsuccessful or has an error
je_idstringOptional

Required only if success parameter is set to true. Value of je_id is the resulting id of the JE posting in the ERP system. This will create link between Gappify QJE and ERP JE.

error_detailsstringOptional

If the JE posting is unsuccessful or has an error, provide the reason which will be available for the users to fix and repost the JE.

Response

Journal entry updated successfully.

request_idUUID

Unique identifier for the request

status"IN_PROGRESS"

Status of the request

Errors