client.events()
Çdo metodë në këtë hapësirë emrash: nënshkrimi, parametrat, çfarë kthen dhe një shembull.
Metodat
Things your contacts did, sent by your own code, such as an order placed or a trial started. An event starts the automations whose trigger names it and ends the waits that were holding out for it.
events().send
Record that something happened to a contact
Map<String, Object> send(Map<String, Object> body, RequestOptions options)Records an event against one contact, named by email or contactId: an order placed, a trial started, a plan changed. Every live automation whose trigger is this event name, and whose filters match properties, takes the contact in, and any wait step holding out for the name moves on. enrolled and resumed in the answer say what it set off. Events are kept for 90 days.
Every call carries an Idempotency-Key. The SDK generates one per call and reuses it on that call's retries, so a retried network failure returns the stored event instead of recording a second one. Pass idempotencyKey to extend that across processes and restarts. A replay returns replayed set to true and starts nothing again. The same key with a different event is a 422 idempotency_key_reuse.
An event sent with a test key is stored with mode test and starts or resumes nothing.
Parametrat
body.nameStringE detyrueshmeWhat happened, such as
order.placed: 1 to 100 letters, digits, dots, colons, dashes and underscores, starting with a letter or a digit. Names are matched exactly, case included.body.emailStringThe contact the event is about, by email address. Send this or
contactId.body.contactIdStringThe contact the event is about, by id. Send this or
email.body.propertiesMap<String, Object>Anything worth keeping about the event, as a map of at most 50 keys and 4 KB of JSON. An event trigger can filter on these, and steps can put them in an email or a contact field.
body.occurredAtInstant or StringWhen it happened, as an
Instantor an ISO 8601 string. Left out, it is now. It cannot be in the future or more than 90 days ago.body.createContactbooleanAdd the address to the contacts when nobody has it yet. It needs
email. Left out or false, an unknown address is a 404contact_not_found.body.contactNameStringThe name to give a contact that
createContactadds, at most 200 characters.options.idempotencyKeyStringYour own key, 1 to 255 characters of letters, digits,
_,.,:or-. Anything else is a 400invalid_idempotency_key.options.apiKeyStringOverrides the client's API key for this call only.
Kthen
A map: the event, with id, contactId, email, name, properties, occurredAt, mode and createdAt, plus replayed, enrolled, the ids of the automations it put the contact into, and resumed, how many waits it ended.
Shembull
Map<String, Object> event = client.events().send(Body.of( "name", "order.placed", "email", "[email protected]", "properties", Body.of("orderId", "AC-4192", "total", 129), "createContact", true), RequestOptions.create().idempotencyKey("order:AC-4192:placed")); System.out.println(event.get("id") + " " + event.get("enrolled") + " " + event.get("resumed") + " " + event.get("replayed"));Shënime
A name, properties or an
occurredAtthat break a rule, or a body that names no contact, is 422invalid_eventwithparamnaming the field.A key or an app may send 600 events a minute. Past that the call is 429
event_rate_limited.An app a member connected reaches only the contacts that member added, and a contact it creates belongs to that member.
Retried automatically on network failure and retryable statuses, because the idempotency key makes a retry safe.
E disponueshme edhe në
- API
POST /events- TypeScript
events.send()- Python
events.send()- Ruby
events.send- PHP
events->send- Go
Events.Send- C#
Events.SendAsync- CLI
openemail events send
events().sendBatch
Record up to 100 contact events in one call
Map<String, Object> sendBatch(List<Map<String, Object>> events, RequestOptions options)Records each event in order, as if events().send had been called for it, and reports per event. It is never all or nothing: accepted holds the events that were stored and failed the ones that were not, each with the index it had in the list, so one unknown address does not stop the rest. The call returns whenever the batch was processed, so check failed rather than relying on an exception.
The batch shares one Idempotency-Key, generated once per call or supplied as idempotencyKey, and the server remembers each event under the key and its position. Retrying the same list replays the events that were already stored and records only the ones that were not. Reordering the list between attempts makes an event that moved fail with idempotency_key_reuse.
Parametrat
eventsList<Map<String, Object>>E detyrueshmeThe events, 1 to 100 of them, each in the shape
events().sendtakes:name,emailorcontactId, and optionallyproperties,occurredAt,createContactandcontactName.options.idempotencyKeyStringYour own key for the whole batch, 1 to 255 characters of letters, digits,
_,.,:or-.options.apiKeyStringOverrides the client's API key for this call only.
Kthen
A map with accepted, a list of the stored events, each shaped like what events().send returns plus its index, and failed, a list of maps with index, code and message.
Shembull
Map<String, Object> batch = client.events().sendBatch(List.of( Body.of("name", "trial.started", "email", "[email protected]"), Body.of("name", "trial.started", "email", "[email protected]", "properties", Body.of("plan", "team"))), RequestOptions.create().idempotencyKey("trials:2026-10-11")); if (batch.get("failed") instanceof List<?> failures) { for (Object failure : failures) { System.out.println(failure); }} System.out.println(batch.get("accepted"));Shënime
A body of the wrong shape, an empty list or more than 100 events is refused whole with 422
invalid_parameter, andparamnames the event and the field, such asevents.3.name.The batch counts as that many events toward the 600 a minute a key or an app may send. A batch that would pass it is 429
event_rate_limitedand nothing is stored.A failed event carries the code the single call would answer:
invalid_event,contact_not_foundoridempotency_key_reuse.Retried automatically on network failure and retryable statuses, because the idempotency key makes a retry safe.
E disponueshme edhe në
events().listNames
List the event names the workspace has seen
List<Map<String, Object>> listNames(RequestOptions options)Returns the distinct names of the events the workspace holds, in byte order, at most 100. It is what the app suggests when somebody picks the event that starts an automation. Events are kept for 90 days, so a name nothing has sent in that time is gone. The list is not paginated.
Parametrat
options.apiKeyStringOverrides the client's API key for this call only.
Kthen
A list of maps, each with name.
Shembull
List<Map<String, Object>> names = client.events().listNames(); for (Map<String, Object> entry : names) { System.out.println(entry.get("name"));}Shënime
It needs
automations:read, not a contacts scope, because it serves the automation builder.Read only, so the SDK retries it after a network failure like any other read.