From 3c5cd9045752faea188f4abc4f29911e13cbe3b9 Mon Sep 17 00:00:00 2001 From: Eileen McNaughton <emcnaughton@wikimedia.org> Date: Mon, 21 Oct 2019 12:18:48 +1300 Subject: [PATCH] Update docs/financial/OrderAPI.md Co-Authored-By: Mikey O'Toole <mikey@mjco.uk> --- docs/financial/OrderAPI.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/financial/OrderAPI.md b/docs/financial/OrderAPI.md index b848802b..911148ae 100644 --- a/docs/financial/OrderAPI.md +++ b/docs/financial/OrderAPI.md @@ -5,7 +5,7 @@ An 'order' is our developer term for a pseudo-entity that maps to the CiviCRM contribution object but also encompasses related entities like line items, memberships, event registrations and underlying financial entities. There is no single 'order' table but the top level order information is stored in the civicrm_contribution table. -The Order API is intended to be used as the primary API for adding, updating, and deleting orders. When using the order api you should +The Order API is intended to be used as the primary API for adding, updating, and deleting orders. When using the Order API you should: 1. Rely on the Order API to create related objects like line items, memberships and event registrations. (Don't pre-create them) 2. Always create orders in a pending state (unfortunately you need to pass contribution_status_id = Pending in for historical reasons). -- GitLab