Welcome

This documentation was last updated on Tue Feb 23 13:54:56 GMT 2021 and covers Mambu Version v9.85.0

Welcome to the Mambu Streaming API documentation!

Our streaming API is independent from the existing Mambu API and WebHook infrastructure and allows you to subscribe to constant, real-time updates of activities within Mambu. If your connection is interrupted for any reason, your cursor position is saved so that when you re-connect, you will pick up exactly where you left off. Please read on to learn more about how to use the streaming API and for a full reference of each endpoint.

Java Sample Client

To help get you started quickly, a sample project (in Java) implementing a Streaming API client is available at https://github.com/mambu-gmbh/Streaming-API-Java-Sample-Client.

Using the Streaming API

Creating Subscriptions

Request

Sample Request

curl -v -XPOST "https://demotenant.localhost:8889/api/v1/subscriptions" -H "Content-type: application/json" -d

Body Parameter

{
    "owning_application": "demo-app",
    "event_types": ["mrn.event.demotenant.streamingapi.client_approved"]
}

A Subscription can be created by sending a POST request to the /api/v1/subscriptions resource.

Response

Sample Response

{
  "owning_application": "demo-app",
  "event_types": [
    "mrn.event.demotenant.streamingapi.client_approved"
  ],
  "consumer_group": "default",
  "read_from": "end",
  "id": "0691160a-b519-4595-b85c-a400fc73e963",
  "created_at": "2018-11-18T22:27:29.156Z"
}

The response returns the whole Subscription object that was created, including the server generated id field:

Deleting Subscriptions

Request

Sample Request

curl -X DELETE /api/v1/subscriptions/071569bc-89f2-4b52-8277-6ed9614ffbb3

A Subscription can be removed by sending a DELETE request to the /api/v1/subscriptions/{subscription_id} resource.

Response

Sample Response

{
    "title": "Not Found",
    "status": 404,
    "detail": "Subscription with id \"071569bc-89f2-4b52-8277-6ed9614ffbb3\" does not exist"
}

The possible responses for the delete are:

204: The subscription has been successfully deleted.
404: The subscription does not exist, along with this error message a response body is received.

Consuming Events from a Subscription

Request

Sample Request

curl -v -XGET "https://.demotenant.localhost:8889/api/v1/subscriptions/0691160a-b519-4595-b85c-a400fc73e963/events"

Consuming events is achieved by sending a GET request to the Subscription’s event resource /api/v1/subscriptions/{subscription-id}/events.

Response

Sample Response

HTTP/1.1 200 OK
X-Mambu-StreamId: 93ae5174-b863-4f8f-ba33-d274854d1f3d
Transfer-Encoding: chunked

{ "cursor" : {    "partition": "1",    "offset": "001-0001--1",    "event_type": "mrn.event.demo_tenant.streamingapi.client_approved",    "cursor_token": "1d23d044-daa1-414c-8ec4-a060ba03d77c"  },  "info": {    "debug": "Stream started"  }}
{ "cursor" : {    "partition": "1",    "offset": "001-0001-000000000000000000",    "event_type": "mrn.event.demo_tenant.streamingapi.client_approved",    "cursor_token": "e8f6bc5d-65b7-4466-9d95-507da0e79d3c"  },  "events": [    {      "metadata": {        "occurred_at": "2018-11-18T22:50:12.602Z",        "eid": "fde622d5-f975-4786-8e1d-d328c29761f9",        "event_type": "mrn.event.demo_tenant.streamingapi.client_approved",        "partition": "1",        "received_at": "2018-11-18T22:50:12.786Z",        "flow_id": "jOK94UJFdtKsthWOgOJCwuGC",        "version": "1.0.0"      },      "occurred_at": "2018-11-18T22:50:12.602Z",      "body": "Client was approved notification body",      "content_type": "text/plain; charset=UTF-8",      "template_name": "Demo Template 1",      "category": "DATA"    }  ]}
{ "cursor" : {    "partition": "1",    "offset": "001-0001-000000000000000000",    "event_type": "mrn.event.demo_tenant.streamingapi.client_approved",    "cursor_token": "5fed7de4-86ec-464f-92f0-5d6103869385"  }}

The response is a stream that groups events into JSON batches separated by an endline (\n) character. The output can be seen in the right panel.

Each batch contains the following fields:

cursor: The cursor of the batch which should be used for committing the batch.
events: The array of events of this batch.
info: An optional field that can hold useful information (e.g. the reason why the stream was closed by Mambu).

Please Note:
When a stream is started, the client receives a header named X-Mambu-StreamId, which must be used when committing cursors (see below).

Subscription Cursors

Cursor Structure

{
  "partition": "1",
  "offset": "001-0001-000000000000000000",
  "event_type": "mrn.event.demo_tenant.streamingapi.client_approved",
  "cursor_token": "e8f6bc5d-65b7-4466-9d95-507da0e79d3c"
}

The cursors in the Subscription API have the structure visible to the right →

The fields are:

partition: The partition this batch belongs to. A batch can only have one partition.
offset: The offset of this batch. The offset is server defined and opaque to the client - clients should not try to infer or assume a structure.
event_type: Specifies the event-type of the cursor (as in one stream there can be events of different event-types)
cursor_token: The cursor token generated by Mambu.

Committing Cursors

Request

Sample Request

curl -v -XPOST "https://demotenant.localhost:8889/api/v1/subscriptions/0691160a-b519-4595-b85c-a400fc73e963/cursors"\
  -H "X-Mambu-StreamId: 93ae5174-b863-4f8f-ba33-d274854d1f3d" \
  -H "Content-type: application/json" \
  -d

Body Parameter

{
    "items": [
      {
        "partition": "1",
        "offset": "001-0001-000000000000000000",
        "event_type": "mrn.event.demo_tenant.streamingapi.client_approved",
        "cursor_token": "db4b4c27-f880-4406-a382-b057acf432cd"
      }    ]
  }

Cursors can be committed by posting to Subscription’s cursor resource /api/v1/subscriptions/{subscriptionId}/cursors:

Please be aware that the X-Mambu-StreamId header is required when committing a cursor. The value should be the same as the X-Mambu-StreamId header you receive when opening a stream of events. Also, each client can only commit batches that it has received.

Response

The possible successful responses for a commit are:

204: Cursors were successfully committed and offset was increased.
200: Cursors were committed but at least one of the cursors didn’t increase the offset, since it was less than or equal to the already committed one. The response body will also include json with a list of cursors and the results of their commits.

The timeout for commit is 60 seconds. If you open the stream, read data, and don’t commit anything for 60 seconds - the stream connection will be closed from the Mambu side. Please note that if there are no events available to send and you get only empty batches - there is no need to commit; Mambu will close the connection only if there is some uncommitted data and no commits happened for 60 seconds.

If the connection is closed for any reason, the client still has 60 seconds to commit the events it received from the moment the events were sent. After that, the session will be considered closed and it will be no longer be possible to commit with that X-Mambu-StreamId. If the commit was not made - then the next time you start reading from a subscription you will get data from the last point of your commit, you will receive the events you haven’t committed again and will need to deduplicate.

Streaming API Reference

The purpose of Streaming API is to provide high-performance and reliable mechanism to stream significant amount of data out of Mambu on a constant basis, without posing unnecessary pressure on API and WebHooks infrastructure.

In order to subscribe to Mambu notifications events and consume them, a dedicated API is exposed to be used by clients.

The typical workflow is:

Create a Subscription specifying the topic names you want to read.
Start reading batches of events from the subscription.
Commit the cursors found in the event batches back to Mambu, which will store the offsets.

If the connection is closed, and later restarted, clients will get events from the point the last cursor commit. If you need more than one client for your subscription to distribute the load you can read the subscription with multiple clients, for more details please check the get events endpoint.

Add Subscriptions

POST /subscriptions

This endpoint creates a subscription for event_types.

The subscription is needed to be able to consume events from event_types in a high level way when Mambu stores the offsets and manages the rebalancing of consuming clients.
The subscription is identified by its key parameters (owning_application, event_types, consumer_group).
If this endpoint is invoked several times with the same key subscription properties in body (order of even_types is not important) - the subscription will be created only once and for all other calls it will just return the subscription that was already created.

Example Request

A Subscription

{
  "owning_application": "demo",
  "event_types": [
    "mrn.event.demotenant.streamingapi.client_approved"
  ],
  "consumer_group": "read-product-updates",
  "read_from": "end",
  "initial_cursors": [
    {
      "partition": "1",
      "offset": "001-0001-000000000000000000",
      "event_type": "mrn.event.demotenant.streamingapi.client_approved"
    }
  ]
}

Parameters

Name	Type	Description	In	Required
body	Subscription	Subscription is a high level consumption unit. Subscriptions allow applications to easily scale the number of clients by managing consumed event offsets and distributing load between instances.

The key properties that identify subscription are owning_application, event_types and consumer_group.

It is not possible to have two different subscriptions with these properties being the same.|body|false|

Example Responses

200 :
A subscription

{
  "id": "0691160a-b519-4595-b85c-a400fc73e963",
  "owning_application": "demo",
  "event_types": [
    "mrn.event.demotenant.streamingapi.client_approved"
  ],
  "consumer_group": "read-product-updates",
  "created_at": "1996-12-19T16:39:57-08:00",
  "updated_at": "1996-12-19T16:39:57-08:00",
  "read_from": "end",
  "initial_cursors": [
    {
      "partition": "1",
      "offset": "001-0001-000000000000000000",
      "event_type": "mrn.event.demotenant.streamingapi.client_approved"
    }
  ]
}

201 :
A newly created subscription

{
  "id": "0691160a-b519-4595-b85c-a400fc73e963",
  "owning_application": "demo",
  "event_types": [
    "mrn.event.demotenant.streamingapi.client_approved"
  ],
  "consumer_group": "read-product-updates",
  "created_at": "1996-12-19T16:39:57-08:00",
  "updated_at": "1996-12-19T16:39:57-08:00",
  "read_from": "end",
  "initial_cursors": [
    {
      "partition": "1",
      "offset": "001-0001-000000000000000000",
      "event_type": "mrn.event.demotenant.streamingapi.client_approved"
    }
  ]
}

400 Response

{
  "detail": "string",
  "instance": "http://example.com",
  "status": 0,
  "title": "string",
  "type": "http://example.com"
}

Responses

Status	Meaning	Description	Schema
`200`	OK	Subscription for such parameters already exists. Returns subscription object that already existed.	Subscription
`201`	Created	Subscription was successfuly created. Returns subscription object that was created.	Subscription
`400`	Bad Request	Bad Request	Problem
`422`	Unprocessable Entity	Unprocessable Entity	Problem

Response Headers

Status	Header	Type	Format	Description
200	`Location`	string	uri	The relative URI for this subscription resource.
201	`Location`	string	uri	The relative URI for the created resource.
201	`Content-Location`	string	uri	If the `Content-Location` header is present and the same as the `Location` header the client can assume it has an up to date representation of the Subscription and a corresponding `GET` request is not needed.

Delete Subscription

DELETE /subscriptions/{subscription_id}

This endpoint deletes an existing subscription for event types.

In case the subscription is not needed anymore, it can be manually deleted by providing its unique id.

Parameters

Name	Type	Description	In	Required
subscription_id	string	ID of subscription	path	true

Example Responses

404 :
Subscription ID not found

{
  "title": "Not Found",
  "status": 404,
  "detail": "Subscription with id \"071569bc-89f2-4b52-8277-6ed9614ffbb3\" does not exist"
}

Responses

Status	Meaning	Description	Schema
`204`	No Content	Subscription for the given id has been successfully deleted	None
`404`	Not Found	Subscription for the given id was not found	Inline

Response Schema

Status Code 404

Name	Type	Description	Required	Restrictions
» title	string	A short, summary of the problem type. Written in English and readable for engineers (usually not suited for non technical stakeholders and not localized).	true	none
» status	number	The HTTP status code generated by the origin server for this occurrence of the problem.	true	none
» detail	string	A human readable explanation specific to this occurrence of the problem.	true	none

Cursors

POST /subscriptions/{subscription_id}/cursors

Endpoint for committing offsets of the subscription.

If there is uncommited data, and no commits happen for 60 seconds, Mambu will consider the client to be gone, and will close the connection. As long as no events are sent, the client does not need to commit.
If the connection is closed, the client has 60 seconds to commit the events it received, from the moment they were sent. After that, the connection will be considered closed, and it will not be possible to do commit with that X-Mambu-StreamId anymore.
When a batch is committed that also automatically commits all previous batches that were sent in a stream for this partition.

Example Request

A Cursor

{
  "items": [
    {
      "partition": "1",
      "offset": "001-0001-000000000000000000",
      "event_type": "mrn.event.demotenant.streamingapi.client_approved",
      "cursor_token": "string"
    }
  ]
}

Parameters

Name	Type	Description	In	Required
X-Mambu-StreamId	string	Id of stream which client uses to read events. It is not possible to make a commit for a terminated or none-existing stream. Also the client can't commit something which was not sent to his stream.	header	true
body	object	none	body	false
» items	[object]	List of cursors that the consumer acknowledges to have successfully processed.	body	true
»» partition	string	Id of the partition pointed to by this cursor.	body	true
»» offset	string	Offset of the event being pointed to. Note that if you want to specify beginning position of a stream with first event at offset `N`, you should specify offset `N-1`.	body	true
»» event_type	string	The name of the event type this partition's events belong to.	body	true
»» cursor_token	string	An opaque value defined by the server.	body	true
subscription_id	string	Id of subscription	path	true

Detailed descriptions

»» offset: Offset of the event being pointed to. Note that if you want to specify beginning position of a stream with first event at offset N, you should specify offset N-1.

This applies in cases when you create new subscription or reset subscription offsets.

Also for stream start offsets one can use two special values:

begin - read from the oldest available event.
end - read from the most recent offset.

Example Responses

200 :
A Cursor

{
  "items": [
    {
      "cursor": {
        "partition": "1",
        "offset": "001-0001-000000000000000000",
        "event_type": "mrn.event.demotenant.streamingapi.client_approved",
        "cursor_token": "string"
      },
      "result": "string"
    }
  ]
}

403 Response

{
  "detail": "string",
  "instance": "http://example.com",
  "status": 0,
  "title": "string",
  "type": "http://example.com"
}

Responses

Status	Meaning	Description	Schema
`200`	OK	At least one cursor which was tried to be committed is older or equal to already committed one. Array of commit results is returned for this status code	Inline
`204`	No Content	Offsets were committed	None
`403`	Forbidden	Access forbidden	Problem
`404`	Not Found	Subscription not found	Problem
`422`	Unprocessable Entity	Unprocessable Entity	Problem

Response Schema

Status Code 200

Name	Type	Description	Required	Restrictions
» items	[Cursor-Commit-Result]	[The result of single cursor commit. Holds a cursor itself and a result value.]	true	none
»» cursor	any	none	true	none

allOf

Name	Type	Description	Required	Restrictions
»»» anonymous	object	none	false	none
»»»» cursor_token	string	An opaque value defined by the server.	true	none
»»»» event_type	string	The name of the event type this partition's events belong to.	true	none

and

Name	Type	Description	Required	Restrictions
»»» anonymous	Cursor	none	false	none
»»»» offset	string	Offset of the event being pointed to. Note that if you want to specify beginning position of a stream with first event at offset `N`, you should specify offset `N-1`. This applies in cases when you create new subscription or reset subscription offsets. Also for stream start offsets one can use two special values: - `begin` - read from the oldest available event. - `end` - read from the most recent offset.	true	none
»»»» partition	string	Id of the partition pointed to by this cursor.	true	none

continued

Name	Type	Description	Required	Restrictions
»» result	string	The result of cursor commit. - `committed`: cursor was successfully committed - `outdated`: there already was more recent (or the same) cursor committed, so the current one was not committed as it is outdated	true	none

Events

GET /subscriptions/{subscription_id}/events

Starts a new stream for reading events from this subscription. The data will be automatically rebalanced between streams of one subscription.

The minimal consumption unit is a partition, so it is possible to start as many streams as the total number of partitions in event-types of this subscription.
The rebalance currently only operates with the number of partitions so the amount of data in event-- types/partitions is not considered during autorebalance.
The position of the consumption is managed by Mambu. The client is required to commit the cursors he gets in a stream.

Example Request

GET /api/v1/subscriptions/{subscription_id}/events HTTP/1.1

Accept: application/json
X-Flow-Id: string

Client Rebalancing

If you need more than one client for your subscription to distribute load or increase throughput - you can read the subscription with multiple clients and Mambu will automatically balance the load across them.
Currently, maximum supported number of clients per subscription is equals to number of event types in the subscription multiplied by 3.
For example if there are two event types in the subscription, the total number of clients for the subscription is 6. Total of all partitions within a subscription cannot be more than 100, further this gives a maximum of 33 event types per subscription.
The API provides a guarantee of at-least-once delivery, this means that there are cases where duplicate events may be sent if there are errors committing events - a useful technique to detect and handle duplicates is to be idempotent and to check eid field of event metadata.

Parameters

Name	Type	Description	In	Required
X-Flow-Id	string	The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.	header	false
max_uncommitted_events	string	The maximum number of uncommitted events that Mambu will stream before pausing the stream. When in paused state and commit comes - the stream will resume.	query	false
batch_limit	integer	Maximum number of `event`s in each chunk (and therefore per partition) of the stream.	query	false
stream_limit	integer	Maximum number of `event`s in this stream (over all partitions being streamed in this connection).	query	false
batch_flush_timeout	integer	Maximum time in seconds to wait for the flushing of each chunk (per partition).	query	false
stream_timeout	integer	Maximum time in seconds a stream will live before connection is closed by the server.	query	false
stream_keep_alive_limit	integer	Maximum number of empty keep alive batches to get in a row before closing the connection.	query	false
commit_timeout	string	Maximum amount of seconds that Mambu will be waiting for commit after sending a batch to a client.	query	false
subscription_id	string(uuid)	Id of subscription.	path	true

Detailed descriptions

stream_limit: Maximum number of events in this stream (over all partitions being streamed in this connection).

If 0 or undefined, will stream batches indefinitely.
Stream initialization will fail if stream_limit is lower than batch_limit.

batch_flush_timeout: Maximum time in seconds to wait for the flushing of each chunk (per partition).

If the amount of buffered Events reaches batch_limit before this batch_flush_timeout is reached, the messages are immediately flushed to the client and batch flush timer is reset.
If 0 or undefined, will assume 30 seconds.
Value is treated as a recommendation. Mambu may flush chunks with a smaller timeout.

stream_timeout: Maximum time in seconds a stream will live before connection is closed by the server.

If 0 or unspecified will stream for 1h ±10min.

If this timeout is reached, any pending messages (in the sense of stream_limit) will be flushed to the client.

Stream initialization will fail if stream_timeout is lower than batch_flush_timeout.

If the stream_timeout is greater than max value (4200 seconds) - Mambu will treat this as not specifying stream_timeout.

stream_keep_alive_limit: Maximum number of empty keep alive batches to get in a row before closing the connection.

If 0 or undefined will send keep alive messages indefinitely.

commit_timeout: Maximum amount of seconds that Mambu will be waiting for commit after sending a batch to a client.

In case commit does not come within this timeout, Mambu will initialize stream termination, no new data will be sent. Partitions from this stream will be assigned to other streams.

Setting commit_timeout to 0 is equal to setting it to the maximum allowed value - 60 seconds.

In case low latency is needed, change the commit_timeout to a lower value (e.g. 5 seconds).

Example Responses

200 :
A batch of events

{
  "cursor": {
    "partition": "1",
    "offset": "001-0001-000000000000000000",
    "event_type": "mrn.event.demotenant.streamingapi.client_approved",
    "cursor_token": "string"
  },
  "info": {},
  "events": [
    {
      "metadata": {
        "eid": "105a76d8-db49-4144-ace7-e683e8f4ba46",
        "event_type": "mrn.event.demotenant.streamingapi.client_approved",
        "occurred_at": "1996-12-19T16:39:57-08:00",
        "content_type": "text/plain; charset=UTF-8",
        "category": "string"
      },
      "body": "Client was modified. Activity type: CLIENT_SET_TO_INACTIVE. Date: 27-11-2018.\n",
      "template_name": "Client activity template"
    }
  ]
}

400 Response

{
  "detail": "string",
  "instance": "http://example.com",
  "status": 0,
  "title": "string",
  "type": "http://example.com"
}

Responses

Status	Meaning	Description	Schema
`200`	OK	Stream started. Stream format is a continuous series of `SubscriptionEventStreamBatch` objects separated by `\n`	Subscription-Event-Stream-Batch
`400`	Bad Request	Bad Request.	Problem
`403`	Forbidden	Access forbidden.	Problem
`404`	Not Found	Subscription not found.	Problem
`409`	Conflict	Conflict. There are several possible reasons for receiving this status code: 1) There are no empty slots for this subscriptions. The amount of consumers for this subscription already equals the maximum value - the total number of partitions in this subscription. 2) Request to reset subscription cursors is still in progress.	Problem

Response Headers

Status	Header	Type	Format	Description
200	`X-Mambu-StreamId`	string	uuid	The id of this stream generated by Mambu. Must be used for committing events that were read by client from this stream.

Schemas

Cursor

{
  "offset": "string",
  "partition": "string"
}

Properties

Name	Type	Description	Required	Restrictions
offset	string	Offset of the event being pointed to. Note that if you want to specify beginning position of a stream with first event at offset `N`, you should specify offset `N-1`. This applies in cases when you create new subscription or reset subscription offsets. Also for stream start offsets one can use two special values: - `begin` - read from the oldest available event. - `end` - read from the most recent offset.	true	none
partition	string	Id of the partition pointed to by this cursor.	true	none

Cursor-Commit-Result

{
  "cursor": {
    "cursor_token": "string",
    "event_type": "string",
    "offset": "string",
    "partition": "string"
  },
  "result": "string"
}

The result of single cursor commit. Holds a cursor itself and a result value.

Properties

Name	Type	Description	Required	Restrictions
cursor	Subscription-Cursor	none	true	none
result	string	The result of cursor commit. - `committed`: cursor was successfully committed - `outdated`: there already was more recent (or the same) cursor committed, so the current one was not committed as it is outdated	true	none

Event

{
  "body": "string",
  "metadata": {
    "category": "string",
    "content_type": "application/xml",
    "eid": "110c9a31-71d6-4b55-b88c-65a39248043a",
    "event_type": "string",
    "occurred_at": "2019-08-24T14:15:22Z"
  },
  "template_name": "string"
}

Payload of an Event. Usually represents a status transition in a Business process.

Properties

Name	Type	Description	Required	Restrictions
body	string	Actual content of the notification.	true	none
metadata	Event-Metadata	Metadata for this Event.	true	none
template_name	string	Name of the notification template.	true	none

Event-Metadata

{
  "category": "string",
  "content_type": "application/xml",
  "eid": "110c9a31-71d6-4b55-b88c-65a39248043a",
  "event_type": "string",
  "occurred_at": "2019-08-24T14:15:22Z"
}

Metadata for this Event.

Properties

Name	Type	Description	Required	Restrictions
category	string	Indicates if the content of the notification can be configured in Mambu or it is fixed. Currently only one category is supported: `DATA`	true	none
content_type	string	Notification content format.	true	none
eid	string(uuid)	Unique identifier of this Event. Consumers MIGHT use this value to assert uniqueness of reception of the Event.	true	none
event_type	string	The EventType of this Event.	true	none
occurred_at	string(date-time)	Timestamp of creation of the Event generated by Mambu.	true	none

Enumerated Values

Property	Value
content_type	`application/xml`
content_type	`application/json`
content_type	`text/plain; charset=UTF-8`

Problem

{
  "detail": "string",
  "instance": "http://example.com",
  "status": 0,
  "title": "string",
  "type": "http://example.com"
}

Properties

Name	Type	Description	Required	Restrictions
detail	string	A human readable explanation specific to this occurrence of the problem.	false	none
instance	string(uri)	An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.	false	none
status	integer	The HTTP status code generated by the origin server for this occurrence of the problem.	true	none
title	string	A short, summary of the problem type. Written in English and readable for engineers (usually not suited for non technical stakeholders and not localized).	true	none
type	string(uri)	An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable API documentation for the problem type (e.g., using HTML).	true	none

Stream-Info

{}

This object contains general information about the stream. Used only for debugging purposes. We recommend logging this object in order to solve connection issues.

Clients should not parse this structure.

Properties

None

Subscription

{
  "consumer_group": "string",
  "created_at": "2019-08-24T14:15:22Z",
  "event_types": [
    "string"
  ],
  "id": "string",
  "initial_cursors": [
    {
      "offset": "string",
      "partition": "string",
      "event_Type": "string"
    }
  ],
  "owning_application": "string",
  "read_from": "string",
  "updated_at": "2019-08-24T14:15:22Z"
}

Subscription is a high level consumption unit. Subscriptions allow applications to easily scale the number of clients by managing consumed event offsets and distributing load between instances.

The key properties that identify subscription are owning_application, event_types and consumer_group.

It is not possible to have two different subscriptions with these properties being the same.

Properties

Name	Type	Description	Required	Restrictions
consumer_group	string	The value describing the use case of this subscription. In general that is an additional identifier used to differ subscriptions having the same `owning_application` and `event_types`.	false	none
created_at	string(date-time)	Timestamp of creation of the subscription. This is generated by Mambu. It should not be specified when creating subscription and sending it may result in a client error.	false	read-only
event_types	[string]	EventTypes to subscribe to. The order is not important. Subscriptions that differ only by the order of EventTypes will be considered the same and will have the same id. The size of the `event_type`s list is limited by the total number of partitions within these event types. Default limit for partition count is `100`.	true	none
id	string	ID of subscription that was created. Is generated by Mambu, should not be specified when creating a subscription.	false	none
initial_cursors	[Subscription-Cursor-Without-Token]	List of cursors to start reading from. This property is required when `read_from` = cursors. The `initial` cursors should cover all partitions of subscription. Clients will get events starting from next offset positions.	false	none
owning_application	string	The id of application owning the subscription.	true	none
read_from	string	Position to start reading events from. Currently supported values: - `begin` - read from the oldest available event. - `end` - read from the most recent offset. - `cursors` - read from cursors provided in initial_cursors property. Applied when the client starts reading from a subscription.	false	none
updated_at	string(date-time)	Timestamp of last update of the subscription. This is generated by Mambu. It should not be specified when creating subscription and sending it may result in a client error. Its initial value is same as `created_at`.	false	read-only

Subscription-Cursor

{
  "cursor_token": "string",
  "event_type": "string",
  "offset": "string",
  "partition": "string"
}

Properties

allOf

Name	Type	Description	Required	Restrictions
anonymous	object	none	false	none
» cursor_token	string	An opaque value defined by the server.	true	none
» event_type	string	The name of the event type this partition's events belong to.	true	none

and

Name	Type	Description	Required	Restrictions
anonymous	Cursor	none	false	none

Subscription-Cursor-Without-Token

{
  "offset": "string",
  "partition": "string",
  "event_Type": "string"
}

Properties

allOf

Name	Type	Description	Required	Restrictions
anonymous	Cursor	none	false	none

and

Name	Type	Description	Required	Restrictions
anonymous	object	none	false	none
» event_Type	string	The name of the event type this partition's events belong to.	false	none

Subscription-Event-Stream-Batch

{
  "cursor": {
    "cursor_token": "string",
    "event_type": "string",
    "offset": "string",
    "partition": "string"
  },
  "events": [
    {
      "body": "string",
      "metadata": {
        "category": "string",
        "content_type": "application/xml",
        "eid": "110c9a31-71d6-4b55-b88c-65a39248043a",
        "event_type": "string",
        "occurred_at": "2019-08-24T14:15:22Z"
      },
      "template_name": "string"
    }
  ],
  "info": {}
}

One chunk of events in a stream. A batch consists of an array of events plus a cursor pointing to the offset of the last event in the stream.

The size of the array of event is limited by the parameters used to initialize a Stream.

Sequential batches might present repeated cursors if no new events have arrived.

Properties

Name	Type	Description	Required	Restrictions
cursor	Subscription-Cursor	none	true	none
events	[Event]	[Payload of an Event. Usually represents a status transition in a Business process.]	false	none
info	Stream-Info	This object contains general information about the stream. Used only for debugging purposes. We recommend logging this object in order to solve connection issues. Clients should not parse this structure.	false	none