Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
api:api_journal [2024/01/15 12:10] – [List of journal events] Safak Samilogluapi:api_journal [2024/02/15 10:11] (current) – [Parameters] Lauri Elevant
Line 9: Line 9:
  
 For example, if you want to copy data to your system once an applicant is given a specific offer type, simply poll for the ''Offer was edited: ?'' event. This event is logged each time an offer is edited. If you go over the list of events received, you can easily pick out the ones where the offer type is the one you're looking for and continue to poll more information about these applicants (documents, application data etc.) For example, if you want to copy data to your system once an applicant is given a specific offer type, simply poll for the ''Offer was edited: ?'' event. This event is logged each time an offer is edited. If you go over the list of events received, you can easily pick out the ones where the offer type is the one you're looking for and continue to poll more information about these applicants (documents, application data etc.)
 +
 +**This call will only return events from the last 6 months, for performance reasons.** If you need to access older events, please request an exemption from customer support.
 ==== Syntax ==== ==== Syntax ====
  
Line 19: Line 21:
  
 ^ Name ^  ^ Description ^ Notes ^ ^ Name ^  ^ Description ^ Notes ^
-| ''byEvents''Optional | List of journal events you are interested in | [1] |+| ''byEvents''**Required** | List of journal events you are interested in | [1] |
 | ''bySince'' | Optional | An ISO datetime or the (sequential) ID from which you want to start searching from | [2] | | ''bySince'' | Optional | An ISO datetime or the (sequential) ID from which you want to start searching from | [2] |
 | ''byUntil'' | Optional | An ISO datetime or the (sequential) ID of the last even you wish to receive | [2] | | ''byUntil'' | Optional | An ISO datetime or the (sequential) ID of the last even you wish to receive | [2] |
Line 31: Line 33:
   * // Note [2]: An [[https://en.wikipedia.org/wiki/ISO_8601|ISO 8601 compatible datetime]] (inclusive) or the journal event ID to start from (inclusive). The event ID-s are sequential integers, so you can simply save the last one you processed, and issue the next call with bySince=$lastID+1//   * // Note [2]: An [[https://en.wikipedia.org/wiki/ISO_8601|ISO 8601 compatible datetime]] (inclusive) or the journal event ID to start from (inclusive). The event ID-s are sequential integers, so you can simply save the last one you processed, and issue the next call with bySince=$lastID+1//
   * // Note [3]: For backwards compatibility reasons, the default order/limit are set to  "oldest-first" and 1024, respectively. In many cases, for example when polling for new events,  it makes sense to fetch the last 10 items. In this case, set "order" to "newest-first" and "limit" to 10. //   * // Note [3]: For backwards compatibility reasons, the default order/limit are set to  "oldest-first" and 1024, respectively. In many cases, for example when polling for new events,  it makes sense to fetch the last 10 items. In this case, set "order" to "newest-first" and "limit" to 10. //
-  * // Note [4]: Some elements in the returned objects are links to other API calls. Using the ''expand'' parameter, it is possible to expand this data to the actual records, saving additional API calls. The full list of possible expansions is ''applicant,application,course,institution,invoice,offer,document,flag,tracker''. You can set one or multiple expansions, combining them in a comma-separated fashion to the ''expand'' parameter. Note also that using this parameter caps to ''limit'' to 512 due to performance reasons.// +  * // Note [4]: Some elements in the returned objects are links to other API calls. Using the ''expand'' parameter, it is possible to expand this data to the actual records, saving additional API calls. The full list of possible expansions is ''applicant,application,course,institution,invoice,offer,document,flag,tracker''. You can set one or multiple expansions, combining them in a comma-separated fashion to the ''expand'' parameter. Note also that using this parameter caps to ''limit'' to 512 due to performance reasons. Also note that the ''invoice'' expansion is not available when the API key is limited to an institution.// 
-  * // Note [5]: Some events are not associated with any applications and these filters are thus unavailable. If you choose an incompatible event while also setting the ''byAcademicTermID'' or ''byAcademicYear'' filter, an error will be returned. //+  * // Note [5]: Some events are not associated with any applications and these filters are thus unavailable. If you choose an incompatible event while also setting the ''byAcademicTermID'' or ''byAcademicYear'' filter, an error will be returned.//