We have a workflow where we need to create a ticket for a customer, but the customer and organization may not previously exist. So we also create the organization and customer, and add the customer to the organization. What we are currently doing is:
1. create or update organization (POST /api/v2/organizations/create_or_update)
2. create customer (POST /api/v2/users) or update customer if they exist (PUT /api/v2/users/:customer_id)
3. wait 3 minutes
4. add the customer to the organization membership (POST /api/v2/organization_memberships.json)
5. wait 3 minutes
6. create the ticket using the organization_id and customer_id (as requester_id) (POST
/api/v2/tickets)
We have found that we need to wait because the resources we create are not reliably available immediately. So, if we add the customer to the organization's membership immediately after creating them, one or both of those resources may not be available and we error.
Waiting is causing problems and is just not generally a good pattern. Is there a way I can create these connected resources in one API request? Or a way to know that the resource is available?
Then, as a secondary question, is there a way to do this in bulk (many customers/orgs/tickets)?
