List Events

Retrieves events from a Hipsy organisation.

GET

Query

Arguments

stringrequired

Slug of the organisation whose events should be listed.

string

Which events to return: upcoming, past, or all.

PaginationRequest a specific window of rows with limit and offset. Learn more

number

Maximum number of rows to return.

number

Number of rows to skip.

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Try this request

Request

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/hipsy/0.0.7/actions/list-events" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --get \
  --data-urlencode 'connectionId=$CONNECTION_ID' \
  --data-urlencode 'organisationSlug=' \
  --data-urlencode 'period=upcoming'

{
  "success": true,
  "data": [
    {
      "date": "2026-05-07T12:00:00.000Z",
      "date_until": "2026-05-07T12:00:00.000Z",
      "id": 1,
      "latitude": "string",
      "location": "string",
      "longitude": "string",
      "picture": "string",
      "picture_small": "string",
      "qr_ticketshop": "string",
      "tickets": [
        {}
      ],
      "title": "string",
      "url_hipsy": "string",
      "url_ticketshop": "string"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.