How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Zuora Summary Journal Entries API

A summary journal entry is a summary of Zuora transaction amounts organized by accounting code and general ledger segments. A segment adds more reporting granularity through business dimensions, such as country or product. For more information, see Summary Journal Entries Introduction

Zuora Summary Journal Entries API is one of 80 APIs that Zuora publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Summary Journal Entries. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 5 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 2023-12-15.

Requests are made against a single base URL, https://rest.zuora.com/.

6 operations 5 paths 14 schemas 1 DELETE2 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2023-12-15
Server
https://rest.zuora.com/
Resource Areas
1

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Summary Journal Entries 6

A summary journal entry is a summary of Zuora transaction amounts organized by accounting code and general ledger segments. A segment adds more reporting granularity through busin…

POST
/v1/journal-entries
Create a summary journal entry
POST_SummaryJournalEntry 7 params body → 200
GET
/v1/journal-entries/journal-runs/{jr-number}
List all summary journal entries in a journal run
GET_AllSummaryJournalEntries 9 params → 200
GET
/v1/journal-entries/{je-number}
Retrieve a summary journal entry
GET_SummaryJournalEntry 7 params → 200
DELETE
/v1/journal-entries/{je-number}
Delete a summary journal entry
DELETE_SummaryJournalEntry 7 params → 200
PUT
/v1/journal-entries/{je-number}/cancel
Cancel a summary journal entry
PUT_SummaryJournalEntry 7 params → 200
PUT
/v1/journal-entries/{je-number}/basic-information
Update a summary journal entry
PUT_BasicSummaryJournalEntry 7 params body → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are GETJournalEntriesInJournalRunType (3 properties), CommonResponseType (3 properties), GETJournalEntrySegmentType (2 properties), POSTJournalEntrySegmentType (2 properties). Each schema is shown below with its type and property counts.

POSTJournalEntrySegmentType
object
2 properties 2 required
POSTJournalEntryResponseType
object
2 properties
CommonResponseType
object
3 properties
PUTJournalEntryItemType
GETJournalEntryDetailType
GETJournalEntrySegmentType
object
2 properties
PUT_BasicSummaryJournalEntryType
JournalEntryItemObjectCustomFields
object
Container for custom fields of a Journal Entry Item object.
GETJournalEntriesInJournalRunType
object
3 properties
JournalEntryObjectCustomFields
object
Container for custom fields of a Journal Entry object.
GETJournalEntryDetailTypeWithoutSuccess
GETJournalEntryItemType
POSTJournalEntryType
POSTJournalEntryItemType

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zuora-summary-journal-entries-api-openapi.yml Raw ↑

Other APIs Zuora publishes across the network.

Zuora V1 API
Zuora Accounting Codes API
Zuora Accounting Periods API
Zuora Accounts API
Zuora Actions API
Zuora Aggregate Queries API
Zuora API Health API
Zuora Attachments API
Zuora Bill Run API
Zuora Bill Run Health API
Zuora Billing Documents API
Zuora Billing Preview Run API
Where this information came from

This is an independent, third-party profile of Zuora Summary Journal Entries API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.