---
schema_version: "1"
id: 9f6d83d598bc786c189d331c3732a1dab9a62f145687258ec5581ee1100640ee
title: Configure a Wait Until API Event Activity
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_jb_wait_until_api_event.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_jb_wait_until_api_event.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f7eb98faf02a6da27fee6c25a476e30eb145e9706d55d0f67bc6419abf8fe2bc
description: Follow these steps to configure a Wait Until API Event activity in Journey Builder. This feature uses the same API events configured for journey entry events.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Configure a Wait Until API Event Activity

Follow these steps to configure a Wait Until API Event activity in Journey Builder. This feature uses the same API events configured for journey entry events.

When a journey version containing a Wait Until Event activity goes into a Finishing status, events are ignored. Contacts are held in the Wait Until Event activity and exited at the configured Maximum Wait Duration time.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/images/icon_important.png)

Important If you copy an existing journey and change the copied Wait Until API event, this action impacts other journeys or versions.

Each Wait Until activity can’t exceed 10 events across all journeys.

1. Drag the Wait Until API Event activity onto the canvas.
    
    The system adds a no-event path to the canvas for contacts who don’t respond.
2. Click the wait activity.
3. Select an API event or create one.
4. On the Filter Criteria tab, select the filter criteria.
    
    You can use contact data or journey event data for the filter. Journey event data is related to the API event that you chose rather than the journey’s entry source.
5. Click **Done**.
6. On the Maximum Wait Duration tab, specify the maximum time that contacts are held in this activity before taking the no-event path.
    
    The minimum wait time is one day.
7. Click **Summary** and review your settings.
8. Click **Done**.
    
    Configure the no-event path to reengage customers or have them exit the journey.

#### See Also

- [Create a Filter](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_create_a_filter.htm&release=264.0.0&type=5 "Create a filter to ensure that the intended Marketing Cloud Engagement contact enters your journey, follows a split activity path, or reaches the goal. Use contact data and journey data attributes in a filter as needed.")
- [Journey and Contact Data](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_journey_contact_data.htm&release=264.0.0&type=5 "Journey data preserves the state of a contact's data at the moment an entry event fires, facilitating the use of that data throughout a journey. Contact data captures the data values in the event source data extension at the time when Journey Builder evaluates it. Both are uniquely useful in journey creation.")
- [Admit Contacts Via an API](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_admit_contacts_via_api.htm&release=264.0.0&type=5 "The API event in Journey Builder connects the journey canvas to an API used to admit contacts into a journey. When the API fires an event, the contacts entering the journey are stored in your chosen Marketing Cloud Engagement data extension. You can set a filter using Marketing Cloud Engagement data attributes to ensure that only intended customers enter the journey.")
- [API Event Entry Source Use Case](https://help.salesforce.com/s/articleView?id=mktg.mc_jb_api_entry_source_use_case_1.htm&release=264.0.0&type=5 "A marketer at Northern Trails Outfitters (NTO) works with a developer to set up an API that admits customers into a Marketing Cloud Engagement journey every day. In this example, the marketer and developer work to set up the API Event and API request, and then test sending a single contact into a journey. The API is intended to send a single contact at a time. It admits contacts when they’re ready to enter the journey rather than queuing or batching them.")