Quick Start¶

Getting started with using Activities APIs involves the following steps:

Create an account and a machine user.
Create a JSON Web Token (JWT) by using the machine user credentials.
Make API requests using the JWT.

Note

In the following examples we are:

Making use of a Linux/MacOS shell in which environmental variables are set using the export command. In other environments it may be different, e.g. Windows uses the set command instead.
Using the curl as a client. But the API can be used in any programming language with an HTTP Client, e.g. Go, Python, NodeJS, JavaScript and Java.

Create an account and a machine user¶

The Getting Started page documents the required steps to get a hold of the clientId, clientSecret and partitionId.

Create a token¶

Use the values described in the Authorization section to construct the Create Token request.

Example request¶


export CLIENT_ID=<YOUR_CLIENT_ID>
export CLIENT_SECRET=<YOUR_CLIENT_SECRET>

curl https://siemens-bt-015.eu.auth0.com/oauth/token \
  -H 'content-type: application/json' \
  -d "{
            \"client_id\":\"$CLIENT_ID\",
            \"client_secret\":\"$CLIENT_SECRET\",
            \"audience\":\"https://horizon.siemens.com\",
            \"grant_type\":\"client_credentials\"
      }"

To run this example yourself, set the CLIENT_ID and CLIENT_SECRET first.

Example response¶


{
  "access_token": "eyJ0eXAiOiUSJ9.eyJpc3MiOiJdGlhbHMifQ.MJpcxLfyOt",
  "token_type": "Bearer",
  "expires_in": 86400
}

The token, or JWT (JSON Web Token), is the value of the access_token property in the response. You can now use it by passing it in the Authorization header of any subsequent API requests. The expires_in property represents the number of seconds your token is valid, usually, the value corresponds to 24 hours. When this time has elapsed, you will need to create a new token.

Now you have all you need to start using the API. As a last step of preparation set the token and partitionId as environmental variables.


export PARTITION=<YOUR_PARTITION_ID>
export TOKEN=<YOUR_TOKEN>

Make API requests¶

This guide will take you through the steps you need to:

Consume activities

List Activities¶

To fetch the user performed activities based by PARTITION. size parameter is an optional field and based on this value the response is returned (Note: size should not exceed 1000). cursor represent the last activity id from which the next set of activities can be fetched along with the size parameter. Incase all the activities returned on the current request, the value of next will be null.


curl -H "Authorization: Bearer $TOKEN" \
    "https://securitymanager.siemens.com/sec-activities-v1/partitions/$PARTITION/activities?page[size]=2"

The response contains all details of individual activities.


{
  "links": 
  {
    "self": "/activities?page[size]=2",
    "next": "/activities?page[size]=2&page[cursor]=6478632ea30ccb58b630b273"
  },
  "data": 
  [
    {
      "type": "Activity",
      "id": "6478632ea30ccb58b630b272",
      "attributes": 
      {
        "title": "Identity deleted",
        "description": "Identity Performance Test -
         Security API - First Name Performance Test - Security API -
         Last Name was deleted",
        "eventType": "Operator",
        "severity": "Low",
        "category": "User operation",
        "subCategory": null,
        "created": "2023-06-01T09:21:50.356Z",
        "recorded": "2023-06-01T09:21:52.868Z",
        "subSystem": "Siveillance Access",
        "origin": "Identity Management"
      }
    },
    {
      "type": "Activity",
      "id": "6478632ea30ccb58b630b273",
      "attributes": {
          "title": "Identity created",
          "description": "Identity Performance Test -
           Security API - First Name Performance Test - Security API -
           Last Name was created",
          "eventType": "Operator",
          "severity": "Low",
          "category": "User operation",
          "subCategory": null,
          "created": "2023-06-01T09:21:50.356Z",
          "recorded": "2023-06-01T09:21:50.758Z",
          "subSystem": "Siveillance Access",
          "origin": "Identity Management"
      }
    }
  ]
}

Note

For more details on deprecation policies and common API features such as paging, filtering and errors, refer to the Developer's Guide.