API changelog

1.4.1

• Updated throttle limits - burst: 60/ min and sustained: 43200/ day

1.4.0

• Introduce pagination urls next and/or prev in the response body. These are duplicates of any links already populated in response headers.

1.3.0

• Return last 45 days of data if no date filters provided in the request

1.2.0

• Added supplier external_id to Award response

1.1.0

• Update domain in docs from app.keelvar.com to my.keelvar.app
• Added type and status fields to SourcingEventInclude

1.0.0

• Initial release

1.4.1

• Updated throttle limits - burst: 60/ min and sustained: 43200/ day

1.4.0

• Introduce pagination urls next and/or prev in the response body. These are duplicates of any links already populated in response headers.

1.3.1

• Remove lot from SupplierLotBid schema in API specification making it consistent with API response. The lot_name field can be used to identify lots in an event.

1.3.0

• Return last 45 days of data if no date filters provided in the request

1.2.0

• Added supplier external_id to LatestBids response

1.1.0

• Feed update triggers are extended to include sourcing event publish and resume

1.0.0

• Initial release

2.5.1

• Added category

2.5.0

• Added last_accessed, last_successful_bid, last_failed_bid timestamps

2.4.1

• Updated throttle limits - burst: 60/ min and sustained: 43200/ day

2.4.0

• Feed update triggers are extended to include deleted events

2.3.0

• Added status filter

2.2.0

• Feed update triggers are extended to include draft events

2.1.0

• Introduce pagination urls next and/or prev in the response body. These are duplicates of any links already populated in response headers.

2.0.0

• Deprecated schedule field (made redundant by the rounds field)

1.7.0

• Return last 45 days of data if no date filters provided in the request

1.6.0

• Added supplier external_id to SourcingEvent response

1.5.0

• Added evaluated_scenario_count to SourcingEvent response

1.4.0

• Feed update triggers are extended to include event pause

1.3.2

• Supplier invite_count no longer includes unsent invites

1.3.1

• Fixed bug where multiple records for the same event were being served (ENG-13155)

1.3.0

• Added the rounds fields which will replace the schedule field
• Note that schedule field will be deprecated on December 1, 2024

1.2.1

• Fixed issue where updates weren't being stored in all cases (ENG-12511)

1.2.0

• Added reference_id, is_test, created, published, schedule, closed, created_by, roles, event_contact, lot_count, and scenario_count to SourcingEvent response
• Added invite_count, accepted, and participated to nested supplier entries Note: published, and closed timestamps refer to the most recent time an event was published or closed. i.e. If an event is reopened and closed, the closed timestamp will update

1.1.0

• Added ids for suppliers as part of SourcingEvent response body

1.0.0

• Initial release