Fetch Journal Entry | Build with Bookkeep
Fetch Journal Entry
GET https://api.bookkeep.com/v1/entities/:entity_id/journal_entries/:journal_entry_id
Retrieves the details of a journal entry that has previously been created. Supply the unique entity ID and journal entry ID that was returned from your previous request, and Bookkeep will return the corresponding journal entry information.
Request
Path Parameters
entity_id string required
Unique identifier for the entity.
journal_entry_id string required
Unique identifier for the journal entry.
Responses
- 200
Returns a journal entry if a valid identifier was provided.
- 401
Returns an error if an invalid identifier was provided.
- 404
Returns an error if the journal entry is not found.
- application/json
Schema for Success Response
Schema
id string
Unique identifier for the journal entry.
Example: je_1234567890
entity_id string
Unique identifier for the entity.
Example: ent_1234567890
date string
The date of the journal entry.
Example: 2025-01-15
status string
Status of the journal entry.
Example: posted
memo string
Memo for the journal entry.
Example: Sales summary for Location Name on 2025-01-15
docnumber string
Document number for the journal entry.
Example: JE-2025-001
created_at string
When the journal entry was created.
Example: 2025-01-15T10:30:00Z
updated_at string
When the journal entry was last updated.
Example: 2025-01-15T10:30:00Z
{
"id": "je_1234567890",
"entity_id": "ent_1234567890",
"date": "2025-01-15",
"status": "posted",
"memo": "Sales summary for Location Name on 2025-01-15",
"docnumber": "JE-2025-001",
"created_at": "2025-01-15T10:30:00Z",
"updated_at": "2025-01-15T10:30:00Z"
}
Schema for Error Response
Schema
error object
message string
Example: Journal entry not found
type string
Example: invalid_request_error
{
"error": {
"message": "Journal entry not found",
"type": "invalid_request_error"
}
}
Authorization: http
name: basic
type: http
description: The Bookkeep API uses API keys to authenticate requests. You can view and manage your API keys in the Bookkeep Developer Dashboard. Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. Authentication to the API is performed via HTTP Basic Auth. Provide your Publishable key as the basic auth username value and your Secret key as the basic auth password value. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.
CURL Example
curl -L 'https://api.bookkeep.com/v1/entities/:entity_id/journal_entries/:journal_entry_id' \
-H 'Accept: application/json' \
-H 'Authorization: Basic PHVzZXJuYW1lPjo8cGFzc3dvcmQ+'
Additional Code Examples
- nodejs
- python
- ruby
- csharp
- php